Closed Bug 946250 Opened 11 years ago Closed 11 years ago

Follow up to bug 942140 When settings is invoked from messaging and closed from home button it does not recover its original status

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:1.3+, b2g-v1.3 fixed)

RESOLVED FIXED
1.3 C1/1.4 S1(20dec)
blocking-b2g 1.3+
Tracking Status
b2g-v1.3 --- fixed

People

(Reporter: isabelrios, Assigned: arcturus)

References

Details

(Keywords: regression)

Attachments

(1 file)

12/04 Master build:
Gecko-2dc4d2d
Gaia-573304f

STR:
1. Open messaging app
2. Tap on new message icon or an existing message thread
3. Tap on more options icon "..."
4. Once Messaging settings screen is open, tap on Home key
5. Messaging app is open without user interaction (this is ok), so tap on Home again
6. Then, open Settings app from main menu

EXPECTED
Settings menu is open in Messaging settings view showing its options and buttons correctly.

ACTUAL
Messaging settings menu is open with the close button ('x') instead of the back button ('<').
If you tap on 'x' to close the menu, you are taken to Settings main menu, tapping again in Messaging Settings will open the menu agian with the 'x' button instead of the back ('<') one.
Summary: Follow up to bug 942140 When settings is inoked from messaging and closed from home button it does not recover its original status → Follow up to bug 942140 When settings is invoked from messaging and closed from home button it does not recover its original status
Isabel, do you know if similar issues exist in the SMS app when, for example, you use the "send sms" button in the contacts app?
Assignee: arcturus → francisco.jordano
(In reply to Julien Wajsberg [:julienw] from comment #1)
> Isabel, do you know if similar issues exist in the SMS app when, for
> example, you use the "send sms" button in the contacts app?

Hi Julien,

I did some tests and cannot see something similar.
- Without Messaging app in background: From Contacts tapping on SMS icon the Messaging composer is open with the option to close 'x'. If Messaging app is open and a new Message is created, on the header you see the back button. This happens both closing the Messaging composer by tapping on 'x' or going out by tapping on 'Home' key and then opening Messaging app

But, if -Messaging app is in background:
Tapping on Messaging icon from contacts, the Messaging app is open in the inbox view, not in the composer one. This looks like a regression, if there is not a bug about it, will file a new one.
Thanks! Yes please file this bug :)
Done! Bug 946678
Thanks
(In reply to Isabel Rios [:isabel_rios] from comment #0)
> ACTUAL
> Messaging settings menu is open with the close button ('x') instead of the
> back button ('<').
> If you tap on 'x' to close the menu, you are taken to Settings main menu,
> tapping again in Messaging Settings will open the menu agian with the 'x'
> button instead of the back ('<') one.

Triage: severe user confusion based on comment above.
blocking-b2g: 1.3? → 1.3+
Flags: needinfo?(francisco.jordano)
Attached file Pointer to PR 14461
Attachment #8343730 - Flags: review?(kaze)
Flags: needinfo?(francisco.jordano)
Landed:

https://github.com/mozilla-b2g/gaia/commit/9ef1819d2b5b3d0db48538b6b4b8a0af0440a3c2
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Despite of being 1.3, this bug didn't make it to 1.3 branch, since the tree was closed (being the patch ready).

Noemi, what flags should we use to try to uplift to 1.3?
Flags: needinfo?(noef)
(In reply to Francisco Jordano [:arcturus] from comment #8)
> Despite of being 1.3, this bug didn't make it to 1.3 branch, since the tree
> was closed (being the patch ready).
> 
> Noemi, what flags should we use to try to uplift to 1.3?

Since this bug is a 1.3+ one, there shouldn't be any problem on uplifting it to v1.3 branch, it seems the specific v1.3 status flag has not been created yet ("status-b2g-v1.3") so we can't mark v1.3 as "affected". ni to John Ford, in case he can help us with the uplift to v1.3 branch. Thanks!
Flags: needinfo?(noef) → needinfo?(jhford)
Anyway, the "affected" value does not help uplifting at all. Only the "1.3+" flag and the fact that the "status" flag is not to "fixed". I think we use "status-firefox28" flag for v1.3.

NI John Ford works fine too ;)
Comment on attachment 8343730 [details] [review]
Pointer to PR 14461

Post-mortem r+.
Attachment #8343730 - Flags: review?(kaze) → review+
We must land this patch to v1.3. This is a regression of bug 942140.
Depends on: 942140
Keywords: regression
[v1.3 16a9b1a] Merge pull request #14461 from arcturus/bug-946250
Flags: needinfo?(jhford)
Target Milestone: --- → 1.3 C1/1.4 S1(20dec)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: