+CC Florian, the spec writer. On Tuesday, June 30, 2026 at 9:27:00 PM UTC+9 Yoav Weiss wrote:
> On Tue, Jun 30, 2026 at 2:22 PM Yoav Weiss (@Shopify) < > [email protected]> wrote: > >> >> >> On Friday, June 26, 2026 at 5:41:14 PM UTC+2 Chromestatus wrote: >> >> *Contact emails* >> [email protected], [email protected] >> >> *Explainer* >> https://drafts.csswg.org/css-image-animation-1/explainer >> >> *Specification* >> https://drafts.csswg.org/css-image-animation-1 >> >> *Summary* >> Introduces a new CSS property and pseudo-class to control and detect >> animated images like GIFs and APNGs. 1. image-animation: Can be set to >> "normal", "running", or "paused" to control image animation playback. 2. >> :animated-image: A pseudo-class to determine whether an image is animated. >> >> *Blink component* >> Blink>CSS >> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ECSS%22> >> >> *Web Feature ID* >> Missing feature >> >> *Motivation* >> Currently, user agents autoplay animated images (e.g., GIF, WebP, PNG) by >> default. This behavior can be violate accessibility standards regarding >> pausing and stopping content. Site authors currently lack mechanisms to >> control this playback. The only existing methods are browser-specific >> global settings, which are inconsistent and lack the features needed for >> developers to build accessible, per-image playback interfaces. >> >> *Initial public proposal* >> https://github.com/w3c/csswg-drafts/issues/1615 >> >> *TAG review* >> https://github.com/w3ctag/design-reviews/issues/1237 >> >> >> It seems worthwhile to give the TAG time to review this thoroughly. >> The arguments in Provide this as a UA Setting >> <https://drafts.csswg.org/css-image-animation-1/explainer#provide-this-as-a-ua-setting:~:text=Rejected%20Alternatives-,Provide%20this%20as%20a%20UA%20Setting,-Firefox's%20about:config> >> don't >> clearly outline why e.g. image annotation (as "decorative" vs. "content") >> wouldn't have enabled UA settings to better solve this problem. >> It seems like this solution to a use a11y problem will depend on >> developers doing the right (and highly complex) thing, which feels.. risky >> > > * "user a11y problem" > >> >> >> >> >> >> *TAG review status* >> Pending >> >> *Goals for experimentation* >> None >> >> *Risks* >> >> >> *Interoperability and Compatibility* >> *No information provided* >> >> *Gecko*: No signal (https://github.com/mozilla/standards-positions/ >> issues/1421) >> >> *WebKit*: No signal (https://github.com/WebKit/standards-positions/ >> issues/685) >> >> *Web developers*: No signals >> >> *Other signals*: >> >> *WebView application risks* >> >> Does this intent deprecate or change behavior of existing APIs, such that >> it has potentially high risk for Android WebView-based applications? >> *No information provided* >> >> >> *Debuggability* >> *No information provided* >> >> *Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, ChromeOS, Android, and Android WebView)?* >> Yes >> >> *Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* >> Yes >> >> >> *Flag name on about://flags* >> *No information provided* >> >> *Finch feature name* >> CSSImageAnimation >> >> *Rollout plan* >> Will ship enabled for all users >> >> *Requires code in //chrome?* >> False >> >> *Tracking bug* >> https://issues.chromium.org/u/2/issues/429459566 >> >> *Estimated milestones* >> Shipping on desktop152 Shipping on Android152 Shipping on WebView152 >> >> *Anticipated spec changes* >> >> Open questions about a feature may be a source of future web compat or >> interop issues. Please list open issues (e.g. links to known github issues >> in the project for the feature specification) whose resolution may >> introduce web compat/interop risk (e.g., changing to naming or structure of >> the API in a non-backward-compatible way). >> *No information provided* >> >> *Link to entry on the Chrome Platform Status* >> https://chromestatus.com/feature/5078177326170112?gate=6503444473053184 >> >> *Links to previous Intent discussions* >> Intent to Prototype: https://groups.google.com/a/ >> chromium.org/d/msgid/blink-dev/6968a079.050a0220.307fc3. >> 04ef.GAE%40google.com >> >> >> This intent message was generated by Chrome Platform Status >> <https://chromestatus.com>. >> >> -- >> > You received this message because you are subscribed to the Google Groups >> "blink-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> > To view this discussion visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ec70652d-9d7a-4b5b-8b12-b806abf62e53n%40chromium.org >> >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ec70652d-9d7a-4b5b-8b12-b806abf62e53n%40chromium.org?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/a0f83469-d9a6-4018-b0e2-8e189df2f80en%40chromium.org.
