- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Mar 2024 16:17:30 +0000
- To: public-css-archive@w3.org
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. If "garbage in, garbage out" was actually a motivating principle here, you would not even be clipping, you would display `transparent` or `black` or IACVT. That's what we do for error conditions. Clipping is not error handling; it's *attempting* to show something reasonable, but doing it poorly. So if you’re *already* trying to show something reasonable, I don't understand why you wouldn't want to improve what you do, if it can be done performantly. This does not preclude doing the research for better color spaces to facilitate color manipulation. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9449#issuecomment-2023175774 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 16:17:31 UTC