thunderbird / thunderbird/thunderbird-android
Clarify quotation include/exclude when composing
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 14k
- Forks
- 2.8k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 57
Description
Could we clarify the user interface to make the options of quotations more obvious? To me it looked like a minimize function, instead of an exclude function.
Suggesting tree modifications:
- Change the text "quoted message" to "re-attach quoted message" to clarify that the button has the action of re-attaching. (Or change it to "re-attatch quotation" or "attach quotation". Anyway you get the point.) (Dont forget to inform the translaters about this)
- Change the "X" symbol (cross) to a trashbin symbol, to symbolise discarding the quotation. It won't be confusing to have a trashbin there as it is located next to the edit button and the qoutation is outlined.
- Add a third button, to recover the original quotation. I came up with this to solve an issue I sometimes have where I start editing the quotation and composing a message and later realise I deleted too much in the quotation. A reset button for the quotation area (with a confirm dialog) would resolve that. Just give it some sort of refresh icon. (One might call this an "undo edit" option).
Pretty high standards huh? But why shouldn't we ;)
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
No files or tests are named. Start by locating the quotation controls in the compose message UI and their translation strings; compare the current re-attach, discard, and reset behavior with the three suggestions. Done means the quotation actions are visually distinct, the original quotation can be restored, and translators are informed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- design, internationalization, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100