- From: Lea Verou via GitHub <noreply@w3.org>
- Date: Tue, 07 Oct 2025 14:05:27 +0000
- To: public-css-archive@w3.org
@sh1boot's comment above reminds me that regardless of what we do by default, it would be useful to have syntax for customizing _how_ gamut mapping happens, e.g. what is prioritized. This could also provide an escape hatch for color manipulations now, since it can presumably be implemented sooner. I have recently tried to hack gamut mapping via relative color syntax, and the hooks I had to jump through would make anyone here cry. Given how long implementations have shipped without gamut mapping, we also need a way for authors to detect it. I'm not yet sure what that could be, but I'm throwing it out there in case others have ideas. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9449#issuecomment-3377059317 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 October 2025 14:05:28 UTC