Moving drafts back and forth when closing
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 70/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start in NewMessageModal and Composer, focusing on how draft-body initialization sets this.changed and how onClose uses it. Reproduce the unchanged-draft flow, then verify that closing without edits no longer triggers the local-copy and IMAP-move process while edited drafts retain their existing behavior.
Written by the indexing model from the issue text.
Description
Steps to reproduce
- Open a Draft
- Do nothing (no changes, no modifications)
- Close Draft
Expected behavior
Nothing happens.
Actual behavior
Apparently nothing happens, but the Draft is anyway processed to local copy + move to IMAP even if totally unnecessary. This produce some unpleasant reloading effect in the view.
Mail app version
5.10
Nextcloud version
No response
Mailserver or service
No response
Operating system
No response
PHP engine version
None
Nextcloud memory caching
No response
Web server
None
Database
None
Additional info
The issue mostly lies in NewMessageModal: this.changed is always set to true as a mere effect of initing the body of the draft (in Composer), and this will trigger the whole local copy + move to IMAP process in onClose()
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 364
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 100
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nextcloud/mail
-
1. to develop enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
nextcloud/mail#13841 · 3 comments ·
Maintainers usually reply within 1 day
-
1. to develop enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nextcloud/mail#13828 · 1 comment ·
Maintainers usually reply within 1 day
-
Show email next to name in Search dropdownPossibly taken @vansh-nagar claimed this 20 days ago. Open1. to develop enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
nextcloud/mail#13703 · 1 comment ·
Maintainers usually reply within 1 day
-
ISO-2022-JP emails are garbled in Mail 5.10.12 [Minimal fix available]Possibly taken @neconohitomi claimed this 40 days ago. Open1. to develop bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
nextcloud/mail#13472 · 1 comment ·
Maintainers usually reply within 1 day
-
1. to develop technical debt
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
Similar issues
-
🔧 in development
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
p5.js 2.0+
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
processing/p5.js#9295 · 1 comment ·
Maintainers usually reply within 3 days
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mastra-ai/mastra#27210 · 1 comment ·
Maintainers usually reply within 1 day
-
content html
Difficulty 2/5 1-3 hours Newbie friendliness 82/100