User will get stuck running FTU if he access the utility tray to open settings app

VERIFIED FIXED

Status

Firefox OS
Gaia::System::Window Mgmt
VERIFIED FIXED
4 years ago
4 years ago

People

(Reporter: alive, Assigned: gduan)

Tracking

({regression})

unspecified
ARM
Gonk (Firefox OS)
regression

Firefox Tracking Flags

(blocking-b2g:2.1+, b2g-v1.4 unaffected, b2g-v2.0 unaffected, b2g-v2.1 verified)

Details

Attachments

(1 attachment)

[Blocking Requested - why for this release]:

The is regression from recent app title bar or statusbar work I guess.
STR:
* Flash phone
* Pull down utility tray
* Click settings

Expected:
Cannot access utility tray from FTU

Actual:
User is switched to Settings app and stuck there. Home button doesn't work.
What is expected?
* Avoid utility tray to be opened when running FTU.
* User could check utility tray but cannot launch app from utility tray
* User could launch settings and if she/he launches settings app, stop the FTU and make home button work.
Flags: needinfo?(firefoxos-ux-bugzilla)
Put this bug in your pocket.
Flags: needinfo?(gduan)
Assignee: nobody → gduan
Flags: needinfo?(gduan)

Comment 3

4 years ago
Flagging Jacqueline to double check behavior, but I agree that this should block because the user becomes stuck.
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(jsavory)
QA Wanted for branch checks.
Keywords: qawanted
QA Contact: ckreinbring
I agree that the expected behaviour is correct here. The user should not be able to access the utility tray while going through FTE. I also agree with this being a blocker since it can cause the user to become stuck.
Flags: needinfo?(jsavory)
The bug repros on Flame 2.1 and Buri 2.1

Actual result:  Swiping from the top of the sreen while in FTU can pull down the notification screen and allos the user to enter Settings, where they will become stuck.

Flame 2.1
Build ID: 20140801040326
Gaia: 04ea7e1a4034a50d4a7a4f5b95a04a2ed8313908
Gecko: 104254bd1fc8
Platform Version: 34.0a1
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Buri 2.1
Build ID: 20140801040326
Gaia: 04ea7e1a4034a50d4a7a4f5b95a04a2ed8313908
Gecko: 104254bd1fc8
Platform Version: 34.0a1
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

--------------------------------------------------------------------------------------------------------

The bug does not repro on Flame 2.0 or Flame 1.4

Actual result:  Nothing happens if the user swipes down from the top of the screen while in FTU.

Flame 2.0
Build ID: 20140801000201
Gaia: 1d1a47a1135d8ce44db9b88db4d2ea6f454cf0a8
Gecko: e57d9f525233
Platform Version: 32.0
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Flame 1.4
Build ID: 20140801000200
Gaia: 3feb37ee2ed2319c9e556728723a5517dc1663ea
Gecko: 2b5defe2d811
Platform Version: 30.0
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v1.4: --- → unaffected
status-b2g-v2.0: --- → unaffected
status-b2g-v2.1: --- → affected
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: regression, regressionwindow-wanted
Regression window
Last working
Build ID: 20140724171005
Gaia: c72257b2d27135bfcd68e89dd584182797784016
Gecko: fb981404745a
Platform Version: 34.0a1
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

First broken
Build ID: 20140724174407
Gaia: 62eedafb0657bbec8941f5bdaa919b5a59f25db1
Gecko: 613e79262240
Platform Version: 34.0a1
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Working Gaia / Broken Gecko = No repro
Gaia: c72257b2d27135bfcd68e89dd584182797784016
Gecko: 613e79262240
Broken Gaia / Working Gecko = Repro
Gaia: 62eedafb0657bbec8941f5bdaa919b5a59f25db1
Gecko: fb981404745a
Gaia push log: https://github.com/mozilla-b2g/gaia/compare/c72257b2d27135bfcd68e89dd584182797784016...62eedafb0657bbec8941f5bdaa919b5a59f25db1

B2G-inbound
Last working
Build ID: 20140724124807
Gaia: b9240ad3dbb861c2e98150573ce6e4a64b300abb
Gecko: aa5ab100e231
Platform Version: 34.0a1
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

First broken
Build ID: 20140724131306
Gaia: 62eedafb0657bbec8941f5bdaa919b5a59f25db1
Gecko: 246e007914d1
Platform Version: 34.0a1
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Working Gaia / Broken Gecko = No repro
Gaia: b9240ad3dbb861c2e98150573ce6e4a64b300abb
Gecko: 246e007914d1
Broken Gaia / Working Gecko = Repro
Gaia: 62eedafb0657bbec8941f5bdaa919b5a59f25db1
Gecko: aa5ab100e231
Gaia pushlog: https://github.com/mozilla-b2g/gaia/compare/b9240ad3dbb861c2e98150573ce6e4a64b300abb...62eedafb0657bbec8941f5bdaa919b5a59f25db1
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: regressionwindow-wanted
broken by bug 1042803 ? Etienne can you take a look?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell) → needinfo?(etienne)
We also need to disable ftu in /builds/slave/test/gaia/apps/keyboard/test/marionette/switching_test.js for switch Keyboard App Drag down the utility tray case.

Updated

4 years ago
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Comment on attachment 8466865 [details] [review]
PR to master

Hi Alive,
could you check this patch? Thanks.
Attachment #8466865 - Flags: review?(alive)
Comment on attachment 8466865 [details] [review]
PR to master

Left a proposal on github to improve coupling and semantic.
Attachment #8466865 - Flags: review?(alive) → review+
Thanks Alive,

master: https://github.com/mozilla-b2g/gaia/commit/6badeb901727bb85d558a88a3dd86bed74cf67de
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Flags: needinfo?(etienne)
Resolution: --- → FIXED
Landing this without bug 1048143 would cause perma-red on Gaia-try.
George, could you confirm?
Flags: needinfo?(gduan)
bug 1048143 has landed.
Thanks to George.
Flags: needinfo?(gduan)
Triage: regression.
blocking-b2g: 2.1? → 2.1+
status-b2g-v2.1: affected → fixed
The Utility tray cannot be accessed during the FTU process.

This bug was verified fixed on:

Flame 2.1 (319mb)(Full Flash)

Environmental Variables:
Device: Flame 2.1
BuildID: 20141011000201
Gaia: f5d4ff60ffed8961f7d0380ada9d0facfdfd56b1
Gecko: d813d79d3eae
Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf
Version: 34.0a2 (2.1)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Status: RESOLVED → VERIFIED
QA Whiteboard: [QAnalyst-Triage+][lead-review+] → [QAnalyst-Triage?][lead-review+]
status-b2g-v2.1: fixed → verified
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage?][lead-review+] → [QAnalyst-Triage+][lead-review+]
Flags: needinfo?(ktucker)
You need to log in before you can comment on or make changes to this bug.