Closed
Bug 1198705
Opened 9 years ago
Closed 8 years ago
implement support for script-created KeyframeEffects
Categories
(Core :: DOM: Animation, defect)
Core
DOM: Animation
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox43 | --- | affected |
People
(Reporter: birtles, Assigned: heycam)
References
Details
(Keywords: meta)
This probably involves the following pieces: 1. Implement KeyframeEffectReadOnly.getFrames() http://w3c.github.io/web-animations/#dom-keyframeeffectreadonly-getframes * We should test that we get back expected results for CSS animations / transitions. 2. Implement the KeyframeEffect constructor (and add the interface) http://w3c.github.io/web-animations/#dom-keyframeeffect-keyframeeffect http://w3c.github.io/web-animations/#processing-a-frames-argument http://w3c.github.io/web-animations/#convert-an-ecmascript-keyframe_like-object-to-an-idl-keyframe * Use getFrames() to test that we get back the correct frames. * As a first pass we could simplify this by NOT supporting: - SharedKeyframeList - PropertyIndexedKeyframe - support for animating attributes (i.e. CSS properties only) - 'composite' attribute on a keyframe - null offsets (i.e. spacing) - KeyframeEffectOptions (i.e. just take a double) 3. Implement AnimationEffectReadOnly.computedTiming (bug 1108055) Milan (a volunteer) started work on this with jwatt's help but never finished. 4. Implement support for passing KeyframeEffectOptions to the KeyframeEffect constructor http://w3c.github.io/web-animations/#dictdef-keyframeeffectoptions * Skip: 'spacing', 'composite', 'iterationComposite', 'iterationStart', 'endDelay' * Test using AnimationEffectReadOnly.computedTiming 5. Implement support for null offsets (i.e. distribute spacing) * Test using getFrames() 6. Implement support for PropertyIndexedKeyframe * Test using getFrames()
Assignee | ||
Comment 1•9 years ago
|
||
Turning this into a meta-bug so we can implement the above pieces in their own bugs.
Reporter | ||
Comment 2•8 years ago
|
||
Bug 1211783 tracks the KeyframeEffect interface and now that we can create KeyframeEffectReadOnly objects from script, I think this bug is done.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•