Closed
Bug 1307341
Opened 9 years ago
Closed 7 years ago
Setting non-animated property should not request restyle for throttled animations
Categories
(Core :: DOM: Animation, defect, P3)
Core
DOM: Animation
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: hiro, Unassigned)
Details
Attachments
(1 file)
|
1.36 KB,
patch
|
Details | Diff | Splinter Review |
In bug 1304922 comment 71, Brian noticed me that we have a case that we request a restyle when we have an opacity animation and no transform animation but have an !important transform rule and then remove the important rules like this;
div.animate({ opacity: [0, 1] }, 10000);
div.style.setProperty('transform', 'none', 'important');
after a while
div.style.setProperty('transform', 'translateX(100px)', '');
|
Reporter | |
Comment 1•9 years ago
|
||
It turns out that we request restyle even when we set non animated style to the element which has throttled animations like this;
div.animate({ opacity: [0, 1] }, 1000);
div.style.color = 'red';
Summary: Changing cascade results for transform property should not request restyle for opacity animations running on the compositor → Setting non-animated property should not request restyle for throttled animations
|
||
Updated•9 years ago
|
Priority: -- → P3
|
|
Reporter | |
Comment 2•8 years ago
|
||
A link to a cause that I suspect.
https://bugzilla.mozilla.org/show_bug.cgi?id=1367975#c10
|
|
Reporter | |
Comment 3•7 years ago
|
||
Closing since this bug is specific for the old style system.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•