- From: Eric Portis via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Mar 2024 13:45:16 +0000
- To: public-css-archive@w3.org
@ccameron-chromium I strongly feel that whether an author specifies `oklch(70% 0.34 22)`, `color(rec2020 0.99171 0.13938 0.14796)`, or `color(rgb 123.17% -32.225% 14.91%)`, they've referred to the same point in XYZ space, and a UA trying to map that to a target display has the same (difficult, tradeoff-y) job ahead of it. I don't think there's enough author intent (or, perhaps, lack of intent) in the color syntax chosen to do better things for users depending on what space the author used. I agree that a hue-lightness-chroma space that is bounded to common wider-than-sRGB gamuts, sacrificing perceptual uniformity for author WYSIWYG-certainty, would be a useful thing to add, and should be pursued, outside of this issue. But it won't prevent authors from specifying colors outside of their and their users' display gamuts; tooling can help authors; this issue is about figuring out what to do for users. -- GitHub Notification of comment by eeeps Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9449#issuecomment-2025225382 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 28 March 2024 13:45:16 UTC