Hi,

In the next few days I intend to turn on the Element.getAnimations() and
Document.getAnimations() functions by default for release channels.

This feature allows developers to fetch and manipulate animations generated
using Element.animate() as well as animations created using CSS Animations
or CSS Transitions.

It has been developed behind the dom.animations-api.getAnimations.enabled
preference.

This feature has been implemented in WebKit and Blink but has yet to ship
to their respective release channels. We expect that to happen in the next
version of Safari and shortly after in Chrome.

It has been enabled by default in Nightly for quite some time (Firefox 42
in its earliest form, and Firefox 69 for its current form) but we have been
waiting for WebKit and Blink to implement before shipping.

There are some outstanding spec edits which I hope to finish tomorrow, but
in the absence of those edits both Google and Apple have been using and
extending the web-platform-tests we contributed to this feature.

Bug to turn on by default:
https://bugzilla.mozilla.org/show_bug.cgi?id=1619821

Spec links:
https://drafts.csswg.org/web-animations-1/#dom-animatable-getanimations
https://drafts.csswg.org/web-animations-1/#dom-documentorshadowroot-getanimations
https://drafts.csswg.org/css-transitions-2/
https://drafts.csswg.org/css-animations-2/ (A number of outstanding spec
updates are yet to be merged)

There is no specific intent to prototype these features. They have been
implemented as part of the ongoing work on the Web Animations API.

Please let me know if you have any concerns.

Best regards,

Brian
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to