- From: James Stuckey Weber via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Mar 2024 03:17:19 +0000
- To: public-css-archive@w3.org
> It's clear to a content author when they are going out of the sRGB gamut in `color(srgb R G B)` syntax because their RGB parameters are no longer in `[0,1]`. The problem with `oklch` is that there is no clear signal that the color is unreasonable or non-existent. This is only true of `color(srgb RGB)` because it specifically refers to the smallest gamut. The predefined `display-p3` spaces would have similar guardrails for `p3` capable displays, but not for `sRGB` displays. `color(xyz-d50 0.5 0 0.5)` seems numerically like a reasonable color but is outside the `rec2020` gamut. Given the non-cubic nature of gamuts, I also don't think it is possible to provide a space that simultaneously is perceptually uniform and provides a clear channel-based signal when a color is out of gamut, without removing a significant portion of colors describable by the space within the guardrails. I concur with @facelessuser about the need for tooling for providing guidance around out of gamut colors. Some already exists, and I think additional tooling will emerge as consensus is reached about what happens with out of gamut colors. -- GitHub Notification of comment by jamesnw Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9449#issuecomment-2024324370 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 03:17:20 UTC