- From: Chris Lilley via GitHub <noreply@w3.org>
- Date: Mon, 02 Feb 2026 19:11:12 +0000
- To: public-css-archive@w3.org
This issue was raised before the document was adopted as a CSS ED and refers to wording which has now changed. The [current wording](https://drafts.csswg.org/css-image-animation-1/#valdef-image-animation-running) is: > **running** > Like [normal](https://drafts.csswg.org/css-image-animation-1/#valdef-image-animation-normal), the animation of [animated images](https://drafts.csswg.org/css-image-animation-1/#animated-image) is run normally, as determined by the image format and the host language, > However, animation timelines are scoped per element: among the [content image](https://drafts.csswg.org/css-image-animation-1/#content-image) and [decorative images](https://drafts.csswg.org/css-image-animation-1/#decorative-image) of a single element, any [animated images](https://drafts.csswg.org/css-image-animation-1/#animated-image) with the same [absolute URL](https://url.spec.whatwg.org/#syntax-url-absolute), the same image data, and with an [image-animation](https://drafts.csswg.org/css-image-animation-1/#propdef-image-animation) computed value of [running](https://drafts.csswg.org/css-image-animation-1/#valdef-image-animation-running) must be rendered synchronized to the same timeline as a group, distinct from the timeline of images in other elements, with the timeline starting at the time of the least recent addition to the group. The original question still stands, however. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13429#issuecomment-3837115239 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 2 February 2026 19:11:12 UTC