Closed Bug 983810 Opened 10 years ago Closed 10 years ago

[B2G][FTU] 'Refresh' button is present in the header of every page during First Time Experience

Categories

(Firefox OS Graveyard :: Gaia::First Time Experience, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:1.4+)

RESOLVED WONTFIX
blocking-b2g 1.4+

People

(Reporter: tnguyen, Unassigned)

References

Details

(Keywords: regression, smoketest)

Attachments

(1 file)

Attached image screenshot
Description:
The 'Refresh' button is present on all the pages in the FTE/FTU and can be tapped to refresh Network List. Tapping the button will then display a "Scanning for networks" overlay on the screen. 

Repro Steps:
1) Updated Buri to BuildID: 20140314093423
2) Navigate to Settings app > Device Information > More Information
3) Tap on 'Reset Phone'
4) Tap on 'Reset'

Actual Result: 
'Refresh' button appears in the header of all pages during FTU/FTE

Expected Result:
'Refresh' button doesn't appear in the hader of all during FTU/FTE

Environmental Variables:
Device: Buri Master M-C mozRIL
BuildID: 20140314093423
Gaia: 1cef557f9e9a865d1bf49d99a8f1cca1f0f4f5c4
Gecko: 142911d6d987
Version: 30.0a1
v1.2-device.cfg

Attached: screenshot
QA Contact: pbylenga
Keywords: qaurgent
blocking-b2g: --- → 1.4?
This was definitely caused by bug 968483.
Keywords: qaurgent
Should be fixed per the backout of the above bug - I've asked someone to verify that the issue no longer reproduces with the latest gaia changesets.
Keywords: qawanted
I can verify that the issue no longer reproduces with the latest gaia changesets.

v1.4 Environmental Variables:
Device: Buri v1.4 MOZ
BuildID: 20140313131233
Gaia: d058b4851157dededea27157983087c1920d08da
Gecko: fe40387eba1a
Version: 30.0a1
Firmware Version: v1.2-device.cfg
Keywords: qawanted
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
blocking-b2g: 1.4? → 1.4+
Resolution: WORKSFORME → FIXED
This problem is caused by a style in FTE being overwritten:

/apps/communications/ftu/css/style.css 
line: 163
.no-options header menu {
  display: none;
}

by:
/shared/style/headers.css
line: 135
  order: 3;
  display: flex;
  height: 100%;
  margin: 0;
  padding: 0;
}

The "display: flex" has higher specificity than the style in FTE.  To fix this:
1. We should move the rule in FTU to headers.css
2. Re-write the selector so that it honers the .no-option style.

This will be the fix post 968483 landing, that this is dependent on.
No longer blocks: 968483
Depends on: 968483
Regressions are flagged as blocking the original bug, not dependent. See https://ask.mozilla.org/question/200/should-a-regression-bug-block-or-depend/.
Blocks: 968483
No longer depends on: 968483
Resolving this as WONTFIX for 1.4 since bug #968483 will not be landing.

Jason, if this still occurs in FTE and needs to be fixed separately (i.e. independent of bug #968483) please let UX know.
Flags: needinfo?(kyee)
Resolution: FIXED → WONTFIX
Flags: needinfo?(caseyyee.ca)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: