- From: Christopher Cameron via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Mar 2024 22:33:52 +0000
- To: public-css-archive@w3.org
@LeaVerou said: > A point I made in this discussion that I haven't seen made in the thread: > > @ccameron-chromium: You mentioned several times how being able to specify imaginary or wildly out of gamut colors is "dangerous" because authors are specifying colors without really realizing the actual colors they are specifying, and when display technology evolves, their output will actually be degraded because they were relying on the mapped color. > > However, gamut mapping is a red herring here. As long as you can specify nonexistent colors, you will have this problem _no matter_ what since you have to display them _somehow_. You can have this problem with clipping as well, people can still rely on the clipped color. Yes, this is true. No matter what we do with this sort of input, it's going to be "wrong" by some definition, and clipping is just a "simple wrong". And it's also very hard to identify what input is intentional versus unintentional. This is why I hope that we can put effort into enabling a safe parameter space (be that `okhsl`, or some built-in guardrails for `oklch`). If we fix that problem, then users can take advantage of the nice features of things like relative color syntax, without running this risk. -- GitHub Notification of comment by ccameron-chromium Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9449#issuecomment-2024099800 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 27 March 2024 22:33:53 UTC