Closed Bug 1198024 Opened 9 years ago Closed 9 years ago

[Task Manager] homescreen will flicker when exiting task manager with no apps open

Categories

(Firefox OS Graveyard :: Gaia::System::Task Manager, defect, P3)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:2.5+, b2g-v2.2 unaffected, b2g-master affected)

RESOLVED DUPLICATE of bug 1201099
blocking-b2g 2.5+
Tracking Status
b2g-v2.2 --- unaffected
b2g-master --- affected

People

(Reporter: AdamA, Assigned: etienne)

References

()

Details

(Keywords: regression, Whiteboard: [2.5-Daily-Testing][Spark][Systemsfe])

Attachments

(2 files)

Attached file logcat (deleted) —
Description: When the user is exiting the task manager by pressing the home button and there were no apps open when the task manager was opened the homescreen will flicker duuring the transition back to the homescreen Repro Steps: 1) Update a Aries to 20150824130216 2) Close all apps 3) Hold the home button to open task manager 4) Press the home button to exit task manager 5) Observe screen transition Actual: The Homescreen will flicker when exiting the task manager with no open apps Expected: It is expected that the user cannot see the homescreen flicker when leaving the task manager Environmental Variables: Device: Aries 2.5 [Full Flash] Build ID: 20150824130216 Gaia: d7fb5717d3e0153ac64af2c0d5c11079846d81c3 Gecko: ba43a48d3c52 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: video clip(https://youtu.be/o-MzAQhHGcQ), logcat
This issue DOES occur on Flame 2.5 Environmental Variables: Device: Flame 2.5 [Full Flash] Build ID: 20150824030214 Gaia: cddb9f610cbe03d0ca39d81bbdce46a0fca841ab Gecko: 8a6045d14d6b 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 Homescreen will flicker when exiting the task manager with no open apps ---------------------------------------- This issue DOES NOT occur on Flame 2.2. Environmental Variables: Device: Flame 2.2 [Full Flash] Build ID: 20150821074640 Gaia: 335cd8e79c20f8d8e93a6efc9b97cc0ec17b5a46 Gecko: d29ec25e40e7 Gonk: bd9cb3af2a0354577a6903917bc826489050b40d Version: 37.0 (2.2) Firmware Version: v18D User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 Result: The screen does not flicker when exiting task manager.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: regression
Whiteboard: [2.5-Daily-Testing][Spark][Systemsfe]
Let's get a window.
QA Contact: lixia
b2g-inbound Regression Window: Last Working Environmental Variables: Device: Flame KK 2.5 Build ID 20150713193849 Gaia Revision 7676b68b4d32ed13243eeb719188847121bd5611 Gaia Date 2015-07-13 23:56:32 Gecko Revision https://hg.mozilla.org/integration/b2g-inbound/rev/0931671a14ef Gecko Version 42.0a1 Device Name flame Firmware(Release) 4.4.2 Firmware(Incremental) eng.cltbld.20150810.183734 Firmware Date Mon Aug 10 18:37:46 EDT 2015 Firmware Version v18D v4 Bootloader L1TC000118D0 First Broken Environmental Variables: Device: Flame KK 2.5 Build ID 20150713205349 Gaia Revision 66638d0e65bf58b7f640bcc7bed4a0b23d1356c6 Gaia Date 2015-07-14 03:28:52 Gecko Revision https://hg.mozilla.org/integration/b2g-inbound/rev/5bd5ca3ad614 Gecko Version 42.0a1 Device Name flame Firmware(Release) 4.4.2 Firmware(Incremental) eng.cltbld.20150810.183734 Firmware Date Mon Aug 10 18:37:46 EDT 2015 Firmware Version v18D v4 Bootloader L1TC000118D0 First Broken Gaia & Last Working Gecko - issue DOES repro Gaia Revision 66638d0e65bf58b7f640bcc7bed4a0b23d1356c6 Gecko Revision 0931671a14ef First Broken Gecko & Last Working Gaia - issue DOES NOT repro Gaia Revision 7676b68b4d32ed13243eeb719188847121bd5611 Gecko Revision 5bd5ca3ad614 Gaia pushlog: https://github.com/mozilla-b2g/gaia/compare/7676b68b4d32ed13243eeb719188847121bd5611...66638d0e65bf58b7f640bcc7bed4a0b23d1356c6 Possibly caused by Bug 1179040.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage?][MGSEI-Triage+]
QA Whiteboard: [QAnalyst-Triage?][MGSEI-Triage+] → [QAnalyst-Triage+][MGSEI-Triage+]
Flags: needinfo?(ktucker)
Etienne, can you take a look at this please? This might have been caused by the landing for bug 1179040.
Blocks: 1179040
Flags: needinfo?(etienne)
visual regression
blocking-b2g: --- → 2.5+
Priority: -- → P3
Assignee: nobody → etienne
Flags: needinfo?(etienne)
Comment on attachment 8655978 [details] [gaia] etiennesegonzac:bug-1198024 > mozilla-b2g:master This patch removes an old timeout (from 1 or 2 redesigns of the TaskManager ago ;)). It fixes the issue here, since there was a 100ms delay where the .cards-view class was removed from the #screen (thus displaying #windows and the homescreen inside) but the opening transition of the homescreen (from opacity:0 to opacity:1) wasn't started yet. I tested on both flame and aries with 10 apps open looking carefully at the transition when exiting the card view and I can confirm that this timeout isn't useful anymore.
Attachment #8655978 - Flags: review?(sfoster)
> I tested on both flame and aries with 10 apps open looking carefully at the > transition when exiting the card view and I can confirm that this timeout > isn't useful anymore. First apologies for the delay in getting to this. I can see the flicker without the patch, but looking carefully at the transition with the patch - I see no animation at all. If I break in the debugger in the 'finish' function where we this.element.classList.remove('to-home');, then I *do* see the animation. As I understand it, '_opened' should be fired when the opening animation ends (we pass home-from-cardview.) So we /should/ see the cross-fade as card view fade out (via .to-home) and homescreen fades-in. So I'm not sure yet if I'm just seeing frames get dropped (testing on Flame) or what. That patch looks good as it stands but I'd like to see something fade or understand why it isn't (or having someone assure me it is and its just my old eyes) before landing this.
(In reply to Sam Foster [:sfoster] from comment #9) > > I tested on both flame and aries with 10 apps open looking carefully at the > > transition when exiting the card view and I can confirm that this timeout > > isn't useful anymore. > > First apologies for the delay in getting to this. I can see the flicker > without the patch, but looking carefully at the transition with the patch - > I see no animation at all. If I break in the debugger in the 'finish' > function where we this.element.classList.remove('to-home');, then I *do* see > the animation. As I understand it, '_opened' should be fired when the > opening animation ends (we pass home-from-cardview.) So we /should/ see the > cross-fade as card view fade out (via .to-home) and homescreen fades-in. So > I'm not sure yet if I'm just seeing frames get dropped (testing on Flame) or > what. > > That patch looks good as it stands but I'd like to see something fade or > understand why it isn't (or having someone assure me it is and its just my > old eyes) before landing this. If you saw it skip it means it can skip. I'll fix this issue differently. Thanks!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Comment on attachment 8655978 [details] [gaia] etiennesegonzac:bug-1198024 > mozilla-b2g:master Thanks Etienne, I'll watch that other bug with interest
Attachment #8655978 - Flags: review?(sfoster)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: