Closed Bug 1174810 Opened 9 years ago Closed 9 years ago

[Spark] z-index issue with dialogs/overlays

Categories

(Firefox OS Graveyard :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:2.5+, b2g-master affected)

RESOLVED WORKSFORME
blocking-b2g 2.5+
Tracking Status
b2g-master --- affected

People

(Reporter: justindarc, Unassigned)

References

Details

(Whiteboard: [spark][aries])

In latest Spark/Aries build, there is a random z-index issue with dialog windows and overlays. It does not always occur, but is still fairly easy to reproduce.

STR:
1. Open Settings app
2. Select "Developer" item
3. Open the "Debugging via USB" drop-down
4. Observe the "Debugging via USB" options overlay
5. Long-press "Home" to open Task Manager and kill Settings app
6. Open Settings app
7. Select "Developer" item
8. Open the "Debugging via USB" drop-down
9. Observe a quick flicker of the "Debugging via USB" options overlay and see the overlay disappear into the background (touching anywhere on the screen will bring the overlay into the foreground)
[Blocking Requested - why for this release]: This is really bad and can render the device unusable.
blocking-b2g: --- → spark?
Whiteboard: [spark][aries]
Also, note that the STR above was followed with Customizer disabled.
blocking-b2g: spark? → spark+
I forgot that we can't get regression windows on Aries, yet. QA, could we get a check to see if this repros on Flame?
This does kinda happen on flame; it's not as bad on the flame though.
There has been a mention of the z-bug issue earlier : bug 893920
Fixed by the backout of bug 1161229.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
QA Contact: bzumwalt
For the record this isnt actually z-index - at least in the CSS sense. It seems to be a layout or compositing bug which was exposed by bug 1161229. I'm looking at alternatives that will let me re-land that patch without regressing here. More details in that bug.
Seeing this issue on Flame 3.0

At step 5 of the STR in comment 0, long pressing home button when Debugging via USB picker flashes foreground and background a few times before shrinking to card view.

Device: Flame 3.0
Build ID: 20150616010205
Gaia: 62ba52866f4e5ca9120dad5bfe62fc5df981dc39
Gecko: ce863f9d8864
Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4
Version: 41.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: qaurgent, qawanted
Adding qawanted and verifyme to verify that this has been fixed on the next build.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Keywords: qawanted, verifyme
Issue still reproduces on today's Flame and Spark 3.0

At step 5 of the STR in comment 0, long pressing home button when Debugging via USB picker flashes foreground and background a few times before shrinking to card view.

Also, scrolling in any wheel picker (as in duplicates bug 1174763 and bug 1170793) causes flashing between background and foreground.

Device: Aries 3.0
Build ID: 20150617002346
Gaia: 6271f932e1e918a35ee89f54288bd13385143a71
Gecko: d7c148c84594
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 41.0a1 (3.0)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

Device: Flame 3.0
Build ID: 20150617010205
Gaia: 6271f932e1e918a35ee89f54288bd13385143a71
Gecko: d7c148c84594
Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4
Version: 41.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?][failed-verification]
Flags: needinfo?(ktucker)
Keywords: qawanted, verifyme
QA Whiteboard: [QAnalyst-Triage?][failed-verification] → [QAnalyst-Triage+][failed-verification]
Flags: needinfo?(ktucker)
QA Wanted : please file a new bug in regards to what brogan had suggested if one hasn't been filed already.
Keywords: qawanted
Bug 1161229 has been backed out and I think they're trying to land a fix that could fix this issue and bugs that were duped to this. Removing QAWanted for now and re-opening the bug.
Status: RESOLVED → REOPENED
QA Whiteboard: [QAnalyst-Triage+][failed-verification] → [QAnalyst-Triage?][failed-verification]
Flags: needinfo?(jmercado)
Keywords: qawanted
Resolution: FIXED → ---
Issue appears resolved fixed in RC4 for aries devices
Results: Dialogs/Overlays do not reveal underlaying layer when scrolled

--------------------------------------------------
Environmental Variables:
Device: Aries 3.0
BuildID: 20150619225606
Gaia: 4c06ed88ddccaba8dc941e5006bd2a9e57306f07
Gecko: 7c1a6b1151a1539186b950a144387e2d7f378d1b
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 41.0a1 (3.0) 
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
--------------------------------------------------
Repro: 5/5
QA Whiteboard: [QAnalyst-Triage?][failed-verification] → [QAnalyst-Triage+][failed-verification]
Flags: needinfo?(jmercado)
blocking-b2g: spark+ → 2.5+
If the issue is fixed on RC4, then chances are that it's a dup of one of Sotaro's bugs or an issue with HWC.
Sotaro, is this fixed by one of your recent patches? the bug is not reproducing recently.
Flags: needinfo?(sotaro.ikeda.g)
(In reply to No-Jun Park [:njpark] from comment #17)
> Sotaro, is this fixed by one of your recent patches? the bug is not
> reproducing recently.

My patches are related to hwc, they are not used on dogfooding ROM. The hwc composition is just disabled. It is not clear yet, this bug is related to hwc composition.

I tried the STR on latest master of flame-kk and aries. But 'Long-press "Home" to open Task Manager' did not works...
Flags: needinfo?(sotaro.ikeda.g)
And I saw the problem on master aries/flame-kk with hwc disabled. Therefore my patches for aries seems not related.
1. RC4 has HWC disabled
2. OTA to latest has HWC disabled
3. Reset to Factory settings (HWC becomes enabled) and we can reproduce the z-index issue

In it's current form, this flow (reset to factory settings) isn't part of the smoke test flow so removing keyword.
Keywords: smoketest
On latest master aries/flame-kk, the problem did not happen.
Is this still happening?
Keywords: qawanted
QA Contact: bzumwalt → ddixon
I was unable to reproduce this issue on the latest central Flame and Aries builds listed below.  The overlay in the Developer>Debugging via USB menu works correctly when the user navigates back to Settings and reopens the menu as described in comment 0.  

Environmental Variables:
Device: Aries 2.5
Build ID: 20150806112625
Gaia: 497fe3f938722b0aa49c93f975fad5d9ed3b0a82
Gecko: 22476236b3e1
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 42.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0

Device: Flame 2.5
BuildID: 20150806043003
Gaia: 497fe3f938722b0aa49c93f975fad5d9ed3b0a82
Gecko: 22476236b3e1
Gonk: 41d3e221039d1c4486fc13ff26793a7a39226423
Version: 42.0a1 (2.5) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
QA Whiteboard: [QAnalyst-Triage+][failed-verification] → [QAnalyst-Triage?][failed-verification]
Flags: needinfo?(ktucker)
Keywords: qawanted
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
QA Whiteboard: [QAnalyst-Triage?][failed-verification] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.