Re: [csswg-drafts] [css-images] Disabling image animation (#1615)

As I see it, there are three obvious use-cases:

1. Websites wanting to prevent user-generated content from animating until the viewer OKs it, as can be done with `<video>`. (This one probably doesn't need more than `<img>`, `<embed>`, `<object>`, and maybe SVG `<image>`, but may benefit from being able to toggle instances of the same image separately in some cases.)
2. Websites wanting a means to just prevent user-generated content from animating, period... either as a defense in depth, or to avoid the risk of exposing a 0-day exploit by processing all uploaded user avatars or whatever using something like ImageMagick to chop them down to a single frame. (This would be the quintessential `img { animate: never; }` where toggling is probably not necessary and, even if it is, toggling separate instances independently shouldn't be necessary. As with case 1, the odds of CSS support being necessary are dependent on how often CSS `background-image` and `content` are used to display user-generated content.)
3. Browser extensions, CSS userstyles, or other mechanisms being pressed into service as assistive technologies for people with sensory processing issues. (The `@media (prefers-reduced-motion)` companion, where it's desirable for there to be mechanisms to control *everything* that can run animated images, including `<link rel="icon" ...>`.)

-- 
GitHub Notification of comment by ssokolow
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1615#issuecomment-3051598082 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 9 July 2025 08:03:59 UTC