[Messaging app] 'Back' button should always go back to the overview screen
Bug #1236892 reported by
Christina Li
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu UX |
Fix Released
|
High
|
Olga Kemmet | ||
messaging-app |
Fix Released
|
High
|
Tiago Salem Herrmann | ||
messaging-app (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Current situation:
If the user selected to go view a message from indicators (messaging menu), call log or notification, the 'Back' button takes the user back to the screen he/she previously left the messaging app at (e.g., someone else's thread).
The messaging app only has two levels of structure: 1. Overview and 2. messaging thread
Desired solution:
The 'Back' button is hierarchical and selecting back from the messaging thread should always go to the overview screen, regardless of where the user has come from.
Related branches
lp:~tiagosh/messaging-app/visual-tweaks
- PS Jenkins bot: Needs Fixing (continuous-integration)
- Gustavo Pichorim Boiko (community): Approve
- Bill Filler (community): Approve
-
Diff: 291 lines (+95/-55)5 files modifiedsrc/qml/MainPage.qml (+1/-9)
src/qml/MessageDelegate.qml (+13/-12)
src/qml/Messages.qml (+20/-11)
src/qml/ThreadDelegate.qml (+53/-23)
src/qml/messaging-app.qml (+8/-0)
Changed in ubuntu-ux: | |
assignee: | nobody → Christina Li (christina-li) |
summary: |
- [Messaging app] 'Back button should always go back to the overview + [Messaging app] 'Back' button should always go back to the overview screen |
Changed in messaging-app: | |
assignee: | nobody → Tiago Salem Herrmann (tiagosh) |
importance: | Undecided → High |
Changed in messaging-app: | |
status: | New → Fix Committed |
Changed in messaging-app: | |
status: | Fix Committed → Fix Released |
Changed in messaging-app (Ubuntu): | |
status: | New → Fix Released |
Changed in ubuntu-ux: | |
assignee: | Christina Li (christina-li) → Olga Kemmet (olga-kemmet) |
Changed in ubuntu-ux: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.