Closed
Bug 1112401
Opened 10 years ago
Closed 10 years ago
[Notifications] Opening the Power Saving Mode notification takes user to homescreen
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(blocking-b2g:2.2+, b2g-v2.0M wontfix, b2g-v2.1 unaffected, b2g-v2.2 verified, b2g-master verified)
Tracking | Status | |
---|---|---|
b2g-v2.0M | --- | wontfix |
b2g-v2.1 | --- | unaffected |
b2g-v2.2 | --- | verified |
b2g-master | --- | verified |
People
(Reporter: KTucker, Assigned: mikehenrty)
References
()
Details
(Keywords: regression, Whiteboard: [2.2-exploratory-2][systemsfe])
Attachments
(4 files)
46 bytes,
text/x-github-pull-request
|
alive
:
review+
|
Details | Review |
1.83 KB,
patch
|
bajaj
:
approval-gaia-v2.2+
|
Details | Diff | Splinter Review |
879.36 KB,
video/mp4
|
Details | |
955.34 KB,
video/mp4
|
Details |
When the user taps "Open" on the "Power Saving Mode" notification on the lockscreen, they will be taken to the homescreen. Prerequisite: Power saving mode and lockscreen are enabled. Repro Steps: 1) Updated Flame to Build ID: 20141215040201 2) Restart the phone so that the "Power Saving Mode" notification appears on the lockscreen. 3) Swipe right to left on the notification and tap on "Open". Actual: The user will be redirected to the homescreen. Expected: The user should be taken to the battery section in settings. Environmental Variables Device: Flame 2.2 Master (319mb)(Kitkat Base)(Full Flash) BuildID: 20141216040205 Gaia: af3d2f89f391c92667e04676fc0ac971e6021bb7 Gecko: a3030140d5df Gonk: e5c6b275d77ca95fb0f2051c3d2242e6e0d0e442 Version: 37.0a1 (2.2 Master) Firmware: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 Notes: Repro frequency: 5/5 100% See attached: video
Reporter | ||
Comment 1•10 years ago
|
||
Adding qawanted for branch check.
Reporter | ||
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(dharris)
Comment 2•10 years ago
|
||
I've found that the key to reproing the bug is to set the "Turn on automatically" setting to a threshold higher than the device's current battery level. This will cause the notification to appear when the device is restarted. Able to repro on Flame 2.2 engineering with shallow flash. Actual result: After tapping the Open button on the power save notification, the homescreen appears instead of the Battery page in the Settings. BuildID: 20141217035735 Gaia: d22dfece04fc00457e8369c660c11f945b088d2f Gecko: cb8ad2251c09 Platform Version: 37.0a1 Firmware Version: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 -------------------------------------------------------------------------------------------------------- For 2.1, the user must also unplug their device from a charging source while on the lockscreen in order for the notification to appear. Unable to repro on Flame 2.1 engineering with shallow flash. Actual result: After tapping the Open button on the power save notification, the Battery page will appear. BuildID: 20141216123009 Gaia: b868736aec314c5e69c1329249f170c7b07802ea Gecko: 7b161e9fe25e Platform Version: 34.0 Firmware Version: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.1:
--- → unaffected
Flags: needinfo?(jmitchell)
Keywords: qawanted → regression
QA Contact: ckreinbring
Comment 3•10 years ago
|
||
Blocking on 2.2; regression, broken functionality (of error message)
blocking-b2g: --- → 2.2?
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: regressionwindow-wanted
Comment 5•10 years ago
|
||
https://github.com/mozilla-b2g/gaia/blob/master/apps/system/js/power_save.js#L105 Could you take this issue from here? Thx.
Flags: needinfo?(evanxd)
Updated•10 years ago
|
Assignee: alive → evanxd
Flags: needinfo?(evanxd)
Comment 6•10 years ago
|
||
Regression window Last working BuildID: 20141204080450 Gaia: 0462090a99093049add9268d14cbc7e44c1d1ccb Gecko: 29d086b32a26 Platform Version: 37.0a1 Firmware Version: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 First broken BuildID: 20141205035850 Gaia: 529c5fcd234ffd108b57629673ca97c2ef73376d Gecko: 9eda28f821a2 Platform Version: 37.0a1 Firmware Version: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 Working Gaia / Broken Gecko = No repro Gaia: 0462090a99093049add9268d14cbc7e44c1d1ccb Gecko: 9eda28f821a2 Broken Gaia / Working Gecko = Repro Gaia: 529c5fcd234ffd108b57629673ca97c2ef73376d Gecko: 29d086b32a26 Gaia pushlog: https://github.com/mozilla-b2g/gaia/compare/0462090a99093049add9268d14cbc7e44c1d1ccb...529c5fcd234ffd108b57629673ca97c2ef73376d B2G Inbound Last working BuildID: 20141204082246 Gaia: a208afd47dd0f9633068ada61bc9829b5a2bed7a Gecko: 643a2477719e Platform Version: 37.0a1 Firmware Version: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 First broken BuildID: 20141204090247 Gaia: 256ffaa7ae85bc95cae269482fae7314fdbf2cc6 Gecko: 07a5a56ccf69 Platform Version: 37.0a1 Firmware Version: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 Working Gaia / Broken Gecko = No repro Gaia: a208afd47dd0f9633068ada61bc9829b5a2bed7a Gecko: 07a5a56ccf69 Broken Gaia / Working Gecko = Repro Gaia: 256ffaa7ae85bc95cae269482fae7314fdbf2cc6 Gecko: 643a2477719e Gaia pushlog: https://github.com/mozilla-b2g/gaia/compare/a208afd47dd0f9633068ada61bc9829b5a2bed7a...256ffaa7ae85bc95cae269482fae7314fdbf2cc6
Comment 7•10 years ago
|
||
Bug caused by patch to Bug 1095109 - Since this bug already has someone 'assigned' - no further action at this time.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
QA Contact: ckreinbring
Comment 8•10 years ago
|
||
Looks like this bug is caused by the Notification[1] api. We used the Notification api in bug 1095109. But the Notification's `click` listener in [2] could not be triggered if we create the notification object too early. That's why we could not go to Battery page in settings app after click the notification. If we used this patch[3] to delay 5 seconds(maybe less) to create the notification object, we could not reproduce this bug with following the STR in this bug[4]. Hi Gregor, Do you know that is the Notification issue(too early create notification object and the `click` listener just could not work) a known issue? And how do you think we fix this bug with fixing the Notification bug and no gaia change? Thanks. [1]: https://developer.mozilla.org/en-US/docs/Web/API/notification [2]: https://github.com/mozilla-b2g/gaia/blob/master/apps/system/js/power_save.js#L119 [3]: https://github.com/evanxd/gaia/commit/d870fb26186cc0344ede9c800012874877566b32 [4]: Comment 0
Flags: needinfo?(anygregor)
Updated•10 years ago
|
Summary: [Window Management] Opening the Power Saving Mode notification takes user to homescreen → [Notifications] Opening the Power Saving Mode notification takes user to homescreen
Updated•10 years ago
|
Component: Gaia::System::Window Mgmt → Gaia::System
Updated•10 years ago
|
Blocks: Woodduck
status-b2g-v2.0M:
--- → affected
Assignee | ||
Comment 10•10 years ago
|
||
Still looking at this, so not clearing the ni?. (In reply to Evan Tseng [:evanxd][:愛聞插低] from comment #8) > Do you know that is the Notification issue(too early create notification > object and the `click` listener just could not work) a known issue? And how > do you think we fix this bug with fixing the Notification bug and no gaia > change? This is not a known issue, but I can verify this is what seems to be happening. If this is true, we should fix this in the notification API rather than a workaround in gaia. I'll look at it more tomorrow.
Updated•10 years ago
|
Whiteboard: [2.2-exploratory-2] → [2.2-exploratory-2][systemsfe]
Assignee | ||
Comment 12•10 years ago
|
||
The problem is that power_save.js sends it's notification on boot-up even before mozChromeNotifications has a chance to resend all existing notifications. So the notification gets resent almost immediately, and the notification click observer gets overwritten with null [1]. We can fix this in Gaia for the power save notifications by specifying showOnlyOnce for the mozbehavior. I think we should do this anyway because the power save notification will always get recreated on boot-up by power_save.js, making resending the existing one redundant and confusing. We also need to fix this in Gecko to prevent notifications that are created too early from getting their observers (ie. event handlers) from getting overwritten by the resending logic. I'll look into that after the Gaia fix, probably in a followup. 1.) http://hg.mozilla.org/mozilla-central/file/9155e0c35233/dom/notification/ChromeNotifications.js#l66
Flags: needinfo?(mhenretty)
Assignee | ||
Comment 13•10 years ago
|
||
Attachment #8546921 -
Flags: review?(alive)
Assignee | ||
Comment 14•10 years ago
|
||
Here's the gecko path. Let's get some feedback from Alexandre before continuing with tests. Note, these two patches [gecko and gaia] are completely independent and while they both fix the problem in this bug, they each are for difference reasons and can be landed separately. https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=b81a6c8c0b70
Attachment #8547118 -
Flags: feedback?(lissyx+mozillians)
Comment 15•10 years ago
|
||
Comment on attachment 8546921 [details] [review] [gaia PR] don't resend power save notifications Excellent.
Attachment #8546921 -
Flags: review?(alive) → review+
Comment 16•10 years ago
|
||
(In reply to Michael Henretty [:mhenretty] from comment #14) > Created attachment 8547118 [details] [diff] [review] > [Gecko patch] Don't resend live notifications > > Here's the gecko path. Let's get some feedback from Alexandre before > continuing with tests. > > Note, these two patches [gecko and gaia] are completely independent and > while they both fix the problem in this bug, they each are for difference > reasons and can be landed separately. > > https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=b81a6c8c0b70 Isn't it the solution we considered a workaround in bug 1088224 ?
Updated•10 years ago
|
Flags: needinfo?(mhenretty)
Assignee | ||
Comment 17•10 years ago
|
||
master: https://github.com/mozilla-b2g/gaia/commit/7c5b27cad370db377b18a742d3f3fdb0070e899f this will need uplift. note, if we want to fix this for 2.0m, we will need a different solution.
Assignee | ||
Comment 18•10 years ago
|
||
After speaking to Alexandre on IRC, it seems the workaround we had in bug 1088224 addressed this exact issue. It was for 2.1 only, so we should just backport that. I filed bug 1120598 to track that.
Flags: needinfo?(mhenretty)
Assignee | ||
Comment 19•10 years ago
|
||
Comment on attachment 8547118 [details] [diff] [review] [Gecko patch] Don't resend live notifications [Bug caused by] (feature/regressing bug #): bug 1095109. [User impact] if declined: In certain scenarios, clicking on the power save notification will do nothing. [Testing completed]: Manual testing. Added a unit test. [Risk to taking this patch] (and alternatives if risky): Very low risk since this just changes the mozbehavior field of the power save notification. [String changes made]: none.
Attachment #8547118 -
Flags: feedback?(lissyx+mozillians) → approval-gaia-v2.2?
Updated•10 years ago
|
Attachment #8547118 -
Flags: approval-gaia-v2.2? → approval-gaia-v2.2+
Comment 20•10 years ago
|
||
v2.2: https://github.com/mozilla-b2g/gaia/commit/8b868120ac55de6e0e199acb7b62e89cf4c2cf04
Target Milestone: --- → 2.2 S4 (23jan)
Comment 21•10 years ago
|
||
(In reply to Michael Henretty [:mhenretty] from comment #17) > master: > https://github.com/mozilla-b2g/gaia/commit/ > 7c5b27cad370db377b18a742d3f3fdb0070e899f > > this will need uplift. note, if we want to fix this for 2.0m, we will need a > different solution. Hi Michael, I found 'mozbehavior' doesn't do the trick on 2.0m, do you have any suggestion on how to fix this on 2.0m?
Flags: needinfo?(mhenretty)
Comment 22•10 years ago
|
||
This problem is verified pass on latest build of Flame2.2 See attachments: Flame2.2_video.MP4 Rate: 0/5 Flame 2.2 build: Gaia-Rev f5b3d1b6cfa3e702033f613915ae637cb735cbfb Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/8067c111ddff Build-ID 20150118002501 Version 37.0a2 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20150118.035516 FW-Date Sun Jan 18 03:55:27 EST 2015 Bootloader L1TC000118D0
Updated•10 years ago
|
Updated•10 years ago
|
Flags: needinfo?(mhenretty)
Comment 23•10 years ago
|
||
This issue has been verified successfully on Flame v3.0 See attachment:verify_v3.0.MP4 Rate:0/5 Flame 3.0 build: Gaia-Rev b02ec9713e6de8d96c6954d2c0dfd0442b0656ac Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/38e4719e71af Build-ID 20150126160233 Version 38.0a1 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20150126.192457 FW-Date Mon Jan 26 19:25:08 EST 2015 Bootloader L1TC000118D0
You need to log in
before you can comment on or make changes to this bug.
Description
•