Closed
Bug 1199469
Opened 9 years ago
Closed 7 years ago
[Aries][First Time Experience] The SHB is present in the FTU
Categories
(Firefox OS Graveyard :: Gaia::First Time Experience, defect)
Firefox OS Graveyard
Gaia::First Time Experience
ARM
Gonk (Firefox OS)
Tracking
(b2g-master affected)
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
b2g-master | --- | affected |
People
(Reporter: AdamA, Unassigned)
References
Details
(Whiteboard: [2.5-Daily-Testing][Spark][Systemsfe])
Attachments
(2 files)
Description:
During the FTU users can see the software home button on the bottom of the screen. Pressing the SHB does not do anything.
Repro Steps:
1) Update a Aries to 20150827170205
2) Observe the bottom of the screen during FTU
Actual:
The SHB is present during FTU
Expected:
It is expected that the SHB is not present during the FTU
Environmental Variables:
Device: Aries 2.5 [Full Flash]
Build ID: 20150827170205
Gaia: d784c81961d82cbe9e111405468c590a8345856c
Gecko: ca086f9ef8bc
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 43.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0
Repro frequency: 10/10
See attached: screenshot, logcat
Reporter | ||
Comment 1•9 years ago
|
||
Reporter | ||
Comment 2•9 years ago
|
||
This issue DOES NOT occur on Flame 2.5.
Environmental Variables:
Device: Flame 2.5 [Full Flash]
Build ID: 20150827083151
Gaia: d784c81961d82cbe9e111405468c590a8345856c
Gecko: b33eae31bd71
Gonk: c4779d6da0f85894b1f78f0351b43f2949e8decd
Version: 43.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0
Result:
The SHB cannot be turned on during the FTU.
Blocks: Foxfood-papercuts
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-master:
--- → affected
Flags: needinfo?(ktucker)
Whiteboard: [2.5-Daily-Testing][Spark][Systemsfe]
Comment 3•9 years ago
|
||
Is this a bug? I thought the SHB is functionally equivalent to the hardware home button so it wouldn't make sense to hide it. It might be nice to have some visual feedback to indicate the button has been pressed but its default action has been prevented.
Rob, can you advise or redirect?
Flags: needinfo?(rmacdonald)
Comment 4•9 years ago
|
||
My issue with this is the user cannot go home during the FTE. This will appear like a non functional button to the end user.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Comment 5•9 years ago
|
||
(In reply to KTucker [:KTucker] from comment #4)
> My issue with this is the user cannot go home during the FTE. This will
> appear like a non functional button to the end user.
We could catch the home event and take the user back to the beginning of the FTU (the language page). I still think some affordance to indicate the default action of the home button has been prevent is the best bet. But if UX wants to chime in on possibly hiding the SHB here that would be useful.
Flags: needinfo?(rmacdonald) → needinfo?(jsavory)
Comment 6•9 years ago
|
||
I would say it would be best to simply not display the SHB during FTE, it'll allow for a little more space on each of the screens and it doesn't currently provide any functionality for the user. Once the user reaches the homescreen then the SHB can slide in (unless we allow them to use it during the tutorial but I can't recall what decision we came to on whether it works during the tutorial or not).
I don't think the user would expect the home button to return to the beginning of FTE and that could be very annoying if you did that accidentally.. :)
Flags: needinfo?(jsavory)
Comment 7•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•