Open
Bug 1506765
Opened 6 years ago
Updated 2 years ago
Do an optimization to not flush animations which are running on the compositor in various places where we call FlushPendingNotification
Categories
(Core :: DOM: Animation, enhancement, P3)
Core
DOM: Animation
Tracking
()
People
(Reporter: hiro, Unassigned)
Details
(Keywords: perf:responsiveness)
For example, in Element::GetPrimaryFrame() we have a FlushPendingNotification call but compositor animations never get reframed so we don't need to flush them at all.
Now I guess in most cases we don't need to flush them, just need for event handling places?
Updated•6 years ago
|
Whiteboard: [qf] → [qf:p2:responsiveness]
Comment 1•6 years ago
|
||
I'm tweaking the summary of this bug a bit; the previous summary could be misunderstood to mean that we want to avoid some work on the compositor thread, but this bug is about avoiding main thread work.
Summary: Do an optimization to not flush animations on the compositor in various places where we call FlushPendingNotification → Do an optimization to not flush animations which are running on the compositor in various places where we call FlushPendingNotification
Reporter | ||
Comment 2•6 years ago
|
||
Thanks, Markus.
I am not yet sure how contribute this optimization in the real world, but as for the GetPrimaryFrame case the function is being called in lots of places for lots of purpose, so if a web site has an infinite transform animation, say a loading state icon, this optimization makes the site much better I think.
Updated•3 years ago
|
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•