- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Feb 2024 17:46:04 +0000
- To: public-css-archive@w3.org
I agree with @ccameron-chromium that people are going to get this wrong, and we're already seeing it. Play with https://gradient.style/ for a bit, and you will generate lovely vibrant gradients… that have very little in common with the actual colors being requested. If you just want a nice vibrant gradient, it works great to crank up the chroma and lightness, and then adjust (arbitrary clipped) hues to get what looks good. But I disagree about the solution to that problem. Gamut mapping isn't just there to help give authors more expected output - it's the only way we can preserve legibility for readers. For the majority of color-use in CSS, maintaining predictable contrast has to be our top priority. That's true in color spaces that are gamut-less, and also when clamping rec-2020 colors for an sRGB display. It doesn't matter how the authors got out of gamut, the priority of CSS should be to maintain contrast as well as possible when it happens. I understand that it's not the right solution for every use-case, in the same way that `overflow:visible` is not always appropriate. But then we should provide an explicit escape-hatch for those situations. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9449#issuecomment-1930459124 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 6 February 2024 17:46:07 UTC