Closed
Bug 827382
Opened 11 years ago
Closed 11 years ago
[Settings] Screen flickers when entering panels
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect, P3)
Tracking
(blocking-basecamp:+)
People
(Reporter: arthurcc, Assigned: etienne)
Details
(Whiteboard: [cr 437586])
Attachments
(2 files, 1 obsolete file)
Reproduce steps: 1. Launch the settings app 2. Click on any panel 3. Observe flickers p.s. After turning off "layers.offmainthreadcomposition.animate-transform", the flicker disappears.
Comment 1•11 years ago
|
||
We would take a patch for this but it's not a blocker for V1
blocking-basecamp: ? → -
tracking-b2g18:
--- → +
Comment 2•11 years ago
|
||
Renominating. Partners brought this up, and it's happening particularly bad as of the last 48-72hrs of builds.
blocking-basecamp: - → ?
We discussed a plan this morning to improve this. kaze can you grab or find someone who can?
Comment 4•11 years ago
|
||
(In reply to Chris Jones [:cjones] [:warhammer] from comment #3) > We discussed a plan this morning to improve this. kaze can you grab or find > someone who can? I thought this was a very recent platform regression but if you have a workaround in mind, I’d be happy to implement it ASAP.
(Before I write this out, keep in mind that we'd like to fix this in the platform but it's very hard.) The plan was to separate the animation into two steps - "peek" phase: move the new panel in by a 1% translation or so - transition phase: on transitionend from "peek", set up the existing transition We use this kind of tactic for homescreen transitions and it's proven really effective.
Comment 6•11 years ago
|
||
Working on it.
Updated•11 years ago
|
blocking-basecamp: ? → +
tracking-b2g18:
+ → ---
Priority: -- → P3
Target Milestone: --- → B2G C4 (2jan on)
Updated•11 years ago
|
Assignee: nobody → kaze
Assignee | ||
Comment 9•11 years ago
|
||
The patch will be for the settings app only, this bug shouldn't block an sms bug.
No longer blocks: 828552
Updated•11 years ago
|
Whiteboard: [cr 437586]
Comment 10•11 years ago
|
||
So is the solution going to be the 1% work-around for 1/15? If so, I presume the e-mail bug should be un-duped or a new one spun off so we can do that too?
Assignee | ||
Comment 11•11 years ago
|
||
(In reply to Andrew Sutherland (:asuth) from comment #10) > So is the solution going to be the 1% work-around for 1/15? If so, I > presume the e-mail bug should be un-duped or a new one spun off so we can do > that too? That what I've been told, so an un-duped seems needed.
Assignee | ||
Comment 12•11 years ago
|
||
cjones' recommended work around, patch cleaned up pairing with Rik, this should be solid :)
Attachment #700472 -
Flags: review?(kaze)
Comment 13•11 years ago
|
||
Comment on attachment 700472 [details] [diff] [review] Patch proposal Review of attachment 700472 [details] [diff] [review]: ----------------------------------------------------------------- nice work, please includ some background information in the JS/CSS files before merging. ::: apps/settings/js/settings.js @@ +515,5 @@ > > // load panel (+ dependencies) if necessary -- this should be synchronous > lazyLoad(newPanel); > > + // switch previous/current/forward classes would you add a reference to the Gecko bug (+ some quick description) please? ::: apps/settings/style/settings.css @@ +40,5 @@ > transition: transform .4s ease; > } > +section[role="region"].peek { > + transform: translateX(+0.1%); > +} same here, please provide an explanation regarding this hack.
Attachment #700472 -
Flags: review?(kaze) → review+
Assignee | ||
Comment 14•11 years ago
|
||
PR: Kaze, want to take a look at the final diff? https://github.com/mozilla-b2g/gaia/pull/7517
Assignee | ||
Comment 15•11 years ago
|
||
Assignee | ||
Updated•11 years ago
|
Attachment #700512 -
Flags: review?(kaze)
Assignee | ||
Updated•11 years ago
|
Attachment #700472 -
Attachment is obsolete: true
Comment 16•11 years ago
|
||
Comment on attachment 700512 [details]
Pointer to gaia
Oh, that’s way better without the 400ms delay. :-)
Attachment #700512 -
Flags: review?(kaze) → review+
Assignee | ||
Comment 17•11 years ago
|
||
https://github.com/mozilla-b2g/gaia/commit/c7eb4ad74e08bc0250267155bfe1322587693127
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 18•11 years ago
|
||
This patch causes the settings app to only show a white screen with current inbound :( I reverted the gaia change on my machine and it works again.
Assignee | ||
Comment 19•11 years ago
|
||
Assignee | ||
Updated•11 years ago
|
Attachment #700940 -
Flags: review?(kaze)
Comment 20•11 years ago
|
||
Comment on attachment 700940 [details] [diff] [review] Followup to fix the regression on inbound Review of attachment 700940 [details] [diff] [review]: ----------------------------------------------------------------- ::: apps/settings/style/settings.css @@ +40,5 @@ > +.uninit section[role="region"], > +.uninit section[role="region"].peek { > + transition: none; > +} > + Would you please add a comment to explain that the 'uninit' class is required to avoid a blank screen on the current branch? (gecko21)
Attachment #700940 -
Flags: review?(kaze) → review+
Assignee | ||
Comment 21•11 years ago
|
||
https://github.com/mozilla-b2g/gaia/commit/35a4cd67741f875fb2bd497c1df09a789ba49250
You need to log in
before you can comment on or make changes to this bug.
Description
•