nextcloud / nextcloud/mail

"Discard changes" when resuming empty composer

Open
#8,544 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug feature:composer
Dominant language
JavaScript
Stars
1k
Forks
348
Avg merge
12h 28m
Merged PRs (30d)
91

Description

Steps to reproduce
  1. Configure two accounts
  2. Click New message
  3. Change sender from first to second account
  4. Click outside the modal to close it
  5. Click New message again
Expected behavior

New composer modal

Actual behavior

Confirm dialogue

image

Mail app version

3.3

Mailserver or service

No response

Operating system

No response

PHP engine version

None

Web server

None

Database

None

Additional info

https://github.com/nextcloud/mail/issues/8338 👀 @st3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the flow from New message through changing the sender, closing the modal, and reopening it, then compare the empty composer state with the confirmation dialog. Use the behavior described here and the related issue #8338 as the starting context. Done means reopening an empty composer shows a new composer modal without a discard confirmation.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.