- From: Stephan Sokolow via GitHub <noreply@w3.org>
- Date: Thu, 04 Sep 2025 09:24:44 +0000
- To: public-css-archive@w3.org
Also, in the context of #11554, I'd like to play "hypothetical user if this goes through". Ahem... > What do I put in my user CSS to convert all `<img>` tags to `<video>` so they can be affected by my companion to turning on `prefers-reduced-motion`? I need it as an assistive technology. More directly, #11554 would only solve one of my two use-cases and only awkwardly and incompletely. 1. As a web developer and a developer of small sites that can afford 'rewrite the world' changes, I *think* all the languages I have access to provide things like [lol_html](https://lib.rs/crates/lol_html) which would let me do a blanket, unconditional "Convert all `img` to `video`. 2. I don't think there's a way to use a `<video>` as a CSS background for use with aspect-preserving fill/fit-to-width hacks. 3. As someone with mild focus issues, it does nothing to provide a "fix it in one place, rather than on a site-by-site basis" replacement for the Firefox extension I lost when they switched to WebExtensions.) In short, I see #11554 as unrelated and irrelevant... but potentially abusable as a *hack* to achieve a fix pending an actual fix. -- GitHub Notification of comment by ssokolow Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1615#issuecomment-3252740306 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 4 September 2025 09:24:45 UTC