- From: Christopher Cameron via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Feb 2024 09:24:25 +0000
- To: public-css-archive@w3.org
> > Content authors are effectively limited to seeing P3 today (for widely available hardware), > Your implied solution of "content authors should be forced to make a color-space breakpoint, creating two versions of sites: the Apple Display P3 one and the legacy sRGB one" is brittle Sorry that I'm not doing a good job of being clear about my suggestion. The point I wanted to emphasize in my next paragraph was: > I've been unable to create a page that is legible in P3 but is not legible in sRGB, irrespective of what gamut mapping is done. That is to say that if authors stay within P3 (and presumably Adobe RGB and probably Rec2020), then their content will be legible on on an sRGB display, regardless of which gamut mapping algorithm is used. The consequence of this is that CSS gamut mapping is primarily solving the problem of fixing up colors that are far outside of existing gamuts (e.g, `oklch(90% 90% 0deg)`) or are physically impossible (e.g, `oklch(10% 90% 0deg)`). My proposal is that authors don't specify physically impossible colors, or colors that are far outside of existing displays' gamuts, and that make some touch-ups to the spec to help authors in this direction. -- GitHub Notification of comment by ccameron-chromium Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9449#issuecomment-1940885862 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 13 February 2024 09:24:27 UTC