Closed
Bug 1398037
Opened 6 years ago
Closed 3 years ago
[meta] Ship more of Animation interface
Categories
(Core :: DOM: Animation, enhancement, P5)
Core
DOM: Animation
Tracking
()
RESOLVED
FIXED
mozilla75
People
(Reporter: birtles, Unassigned)
References
(Depends on 1 open bug)
Details
(Keywords: meta, Whiteboard: [layout:backlog:2020q1])
This is a tracking bug for shipping the next subset of Web Animations API. Specifically, the following: 1) 'ready' and 'finished' promise 2) Support for omitting the 0% or 100% keyframe and using the underlying value 3) Extensions to property-indexed keyframes[1] I imagine we will need at least the following bugs: * Create a pref for switching these parts on * Convert type of Keyframe.offset from double? to double (pending spec changes) * Implement extensions property-indexed keyframes (pending spec changes) * Implement async playback rate changes (pending spec changes) * Bugs for tidying up existing tests [1] See https://github.com/w3c/web-animations/issues/148
Reporter | ||
Comment 1•6 years ago
|
||
(In reply to Brian Birtles (:birtles, away until 19 Sep) from comment #0) > * Convert type of Keyframe.offset from double? to double (pending spec changes) Spec issue: https://github.com/w3c/web-animations/issues/198 > * Implement extensions property-indexed keyframes (pending spec changes) Spec issue: https://github.com/w3c/web-animations/issues/148 > * Implement async playback rate changes (pending spec changes) Spec issue: https://github.com/w3c/web-animations/issues/151
Reporter | ||
Comment 2•6 years ago
|
||
Also: * Drop "pending" playback state? (pending spec changes) Spec issue: https://github.com/w3c/web-animations/issues/196
Updated•4 years ago
|
Summary: (meta) Ship more of Animation interface → [meta] (meta) Ship more of Animation interface
Updated•4 years ago
|
Summary: [meta] (meta) Ship more of Animation interface → [meta] Ship more of Animation interface
Updated•3 years ago
|
Whiteboard: [layout:backlog:2020q1]
Reporter | ||
Comment 4•3 years ago
|
||
(In reply to Hiroyuki Ikezoe (:hiro) from comment #3)
Brian, do we still need to keep this bug open?
No, this is done now. Thanks for the reminder!
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox73:
--- → wontfix
status-firefox74:
--- → wontfix
status-firefox75:
--- → fixed
Flags: needinfo?(brian)
Resolution: --- → FIXED
Target Milestone: --- → mozilla75
Updated•3 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•