thunderbird / thunderbird/thunderbird-android
Forwarding marks as read but leaves Mark as Read button in toolbar
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 14k
- Forks
- 2.8k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 57
Description
Expected behavior
When I open a message, mark it as unread, and then forward it, it gets marked as read again once the compose forward activity appears, but after sending the forward and returning to the original message, the toolbuar still has the Mark as Read button in it, rather than Mark as Unread.
Actual behavior
Either the message should not get marked as read as a consequence of opening the composition activity, or the toolbar should contain the Mark as Unread button (because the message is by that point read) rather than Mark as Read.
Steps to reproduce
- Open a message.
- Use the toolbar to Mark as Unread.
- Confirm that the toolbar contains the Mark as Read button, as expected.
- Issue the Forward command.
- In the composition activity, send the forward e-mail, thus returning to reading the original e-mail.
- In the toolbar, observe that the Mark as Read button is still present.
- Back out to the containing mailbox and observe that the message is actually read, not unread.
Environment
K-9 Mail version: 5.800
Android version: 8.1.0
Account type: IMAP
Contributor 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.
Research direction
Start by reproducing the forward flow described in the issue on Android with K-9 Mail 5.800, observing the toolbar after sending and returning to the original message. Trace the read-state and toolbar update around the forward composition activity. Done means the toolbar and containing mailbox both reflect the message's actual read state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100