Closed
Bug 981401
Opened 10 years ago
Closed 10 years ago
[Messages] Notification does not vanish when the SMS is read when going back from sleep
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect)
Firefox OS Graveyard
Gaia::SMS
Tracking
(blocking-b2g:1.4+, b2g-v1.3T affected, b2g-v1.4 fixed, b2g-v2.0 fixed)
People
(Reporter: julienw, Assigned: steveck)
References
Details
(Keywords: regression)
Attachments
(1 file)
STR: * be on the thread for number A * press the "power" button to put the phone in sleep mode * receive a message from number A * wake up the phone * unlock the device => the notification should be removed This is a regression from the transition to the new Notification API (bug 855165).
Comment 1•10 years ago
|
||
Might be related to the underlying gecko problem in bug 980132.
Reporter | ||
Comment 2•10 years ago
|
||
Nope, this is not the same code path. We're "just" not closing them in that case :(
Comment 4•10 years ago
|
||
The notification is handled by the system app?
Assignee | ||
Comment 6•10 years ago
|
||
Hi Francisco, this patch force to close notification after popup when in the same thread. Might need you help to verify if the solution is safe, thanks.
Attachment #8393580 -
Flags: review?(francisco.jordano)
Flags: needinfo?(schung)
Comment 7•10 years ago
|
||
Comment on attachment 8393580 [details] [review] Link to github Just left a tiny comment on github, also relaunched the marionette test they timed out. Please land once travis is green. Thanks Steve!
Attachment #8393580 -
Flags: review?(francisco.jordano) → review+
Updated•10 years ago
|
status-b2g-v1.3T:
--- → affected
Updated•10 years ago
|
Assignee: nobody → schung
Assignee | ||
Comment 10•10 years ago
|
||
I think the regression(bug 855165) is not uplift to 1.3.
Assignee | ||
Comment 11•10 years ago
|
||
Comment on attachment 8393580 [details] [review] Link to github Hi Francisco, I reset the flag because I consider the visibility and add more related changes for unit test. Thanks for the comments!
Attachment #8393580 -
Flags: review+ → review?(francisco.jordano)
Comment 12•10 years ago
|
||
Comment on attachment 8393580 [details] [review] Link to github \o/ amazing job, and I learned new stuff :) Thanks Steve!
Attachment #8393580 -
Flags: review?(francisco.jordano) → review+
Comment 13•10 years ago
|
||
I forgot, merge once travis green, just saw a ui test failing (not related to your PR)
Assignee | ||
Comment 14•10 years ago
|
||
Landed in master: 26a5e2693df45e095bc8f7b5cc04d19b2c64c9d7 I'll left status unchanged until QA confirms it isn't reproducible on v1.3
Keywords: qawanted
Assignee | ||
Comment 15•10 years ago
|
||
I've verified it's not reproducible on v1.3, so close it as resolved first.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 16•10 years ago
|
||
(In reply to Joe Cheng [:jcheng] from comment #9) > does it really impact 1.3T? 1.3T has this issue.
Flags: needinfo?(james.zhang)
Comment 17•10 years ago
|
||
(In reply to James Zhang from comment #16) > (In reply to Joe Cheng [:jcheng] from comment #9) > > does it really impact 1.3T? > > 1.3T has this issue. 1.3T doesn't have the new notifications API work, so this patch shouldn't be needed on that branch.
Comment 18•10 years ago
|
||
v1.4: 32ddd4e961d9e55749fc3c99e772f41eade8d7dc
Reporter | ||
Comment 19•10 years ago
|
||
(In reply to James Zhang from comment #16) > (In reply to Joe Cheng [:jcheng] from comment #9) > > does it really impact 1.3T? > > 1.3T has this issue. Please file another bug if you have this issue on 1.3T. Maybe we have another 1.3-specific issue.
You need to log in
before you can comment on or make changes to this bug.
Description
•