Closed Bug 980769 Opened 10 years ago Closed 9 years ago

off main thread animations (OMTA, OMT Animations) incorrectly handle multiple animations of the same property and element

Categories

(Core :: CSS Parsing and Computation, defect, P3)

Product:
Core
Component:
CSS Parsing and Computation
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla40

People

(Reporter: dbaron, Assigned: dbaron)

References

Details

As I pointed out in bug 978712 comment 19, the off main thread animation code doesn't correctly handle shipping animations to the compositor when more than one animation influences the value of a property on an element.

For example, consider an element with multiple animations listed in the value of its 'animation' property, all animating opacity, and not all repeating infinitely.  Which one wins should depend on the relevant fill values and which animations are currently running.  The code to handle this doesn't consider any of that.

This might be fixed by bug 847287, but might not, so filing separately.
No longer blocks: 847287
Depends on: 847287
Priority: -- → P4
This should just be fixed by patches in bug 847287 with no extra work here.
fixed by bug 847287
Assignee: nobody → dbaron
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla40
You need to log in before you can comment on or make changes to this bug.