Open
Bug 1039799
Opened 10 years ago
Updated 1 year ago
off-main-thread animations (OMTA, OMT Animations) incorectly handle inheritance of an animating value
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
NEW
People
(Reporter: dbaron, Unassigned)
References
Details
Off main thread animations (OMTA, OMT Animations) incorrectly handle inheritance of a value that's animating, because:
(1) they don't ship the animation to the compositor thread for the child element, but
(2) they suppress the updating on the main thread, which means that only the parent will animate
This is probably a relatively rare case since people don't inherit these properties often, but we should probably handle it in some way, perhaps by avoiding the suppression of main thread updates.
(I've only actually verified that part (1) is a problem; I haven't yet verified that part (2) is a problem; there's a chance it isn't.)
Reporter | ||
Comment 1•10 years ago
|
||
One other thought: fixing this might in some way relate to fixing the cascading levels of transitions and animations (which should probably be separated from bug 960465), since both might depend on having the style rules fill in, in MapRuleInfoInto, a dummy "get from animation" value that gets resolved later instead of filling in the current animating value.
Reporter | ||
Comment 2•9 years ago
|
||
I think this doesn't block shipping OMTA since the properties that are animated off the main thread are so rarely inherited.
Comment 4•8 years ago
|
||
FWIW, Blink doesn't do it right either, but Edge handles it correctly.
Updated•5 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
•