Issue metadata
Sign in to add a comment
|
CSS animation in a descendent of a display:None block triggers a style recalc on every frame. |
||||||||||||||||||||||||
Issue descriptionSee https://b.corp.google.com/issues/32124393 for more details. This structure seems to be causing a style recalc on every frame. This is my guess - I have not yet created a minified repro. Div A - display:None iFrame Div C - infinite CSS animation Once we solve this, we should also add this to the CPU time perf benchmark to prevent future regressions.
,
Oct 29 2016
Neat bug! Is the iframe important to the bug? Is a telemetry benchmark the right place to prevent regressing this? It doesn't seem like a high-level user-centric use-case. Does style calc have LayoutTests or unittests?
,
Oct 30 2016
,
Oct 31 2016
This behaviour can be checked with a layout test (check getAnimations() on the animating element (hidden behind the experimental flag)), a performance test isn't necessary. I think the core of this issue is in how we treat iframes inside display: none elements. If animations are running then presumably everything else in the iframe is behaving like it's not display: none as well. My guess is that frames aren't checking whether their DOM ancestry has display: none when running their document lifecycle.
,
Oct 31 2016
,
Oct 31 2016
,
Nov 1 2016
Issue 656210 has been merged into this issue. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by erikc...@chromium.org
, Oct 28 2016