- From: Christopher Cameron via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 Mar 2024 00:37:20 +0000
- To: public-css-archive@w3.org
I think there might be a miscommunication about what is being proposed here. > > The solution I've been arguing for [above](https://github.com/w3c/csswg-drafts/issues/9449#issuecomment-1981703947) and at the F2F is to provide safe color spaces that can be used in this way without going too far out of a specified gamut (say, sRGB, P3, or Rec2020). We can do this by adding new spaces, or modifying existing ones. > > RGB spaces are awful for creating dynamic variations, which is a pain point authors have had since forever. "Just specify your color in some RGB space" is not the answer. > > Sigh. The only way you could specify colors that stay within these spaces is to use RGB, which as I explained above, is terrible for dynamic variations (and in general for human understanding). The reason I think that there is a miscommunication here is the mentioning of about RGB space. I was aiming at something that is not an RGB space, but rather (for example) `oklch` spaces that are restricted to specific common gamuts. Suppose we create the spaces `oklch-srgb`, `oklch-p3`, and `oklch-rec2020`. They are _exactly_ the `oklch` space, except that they are always gamut mapped to the gamut indicated in their name. Suppose I have a page that I'm developing on a P3 monitor and I want to make sure that the page never goes outside of the P3 gamut (because I don't know what that would look like). I can use `oklch-p3` just like I would use `oklch`, but I can rest assured that the colors will never go outside of the P3 gamut regardless of the capabilities of the display it is displayed on. Does that sound like a useful step to you? Sorry that I haven't had feedback for the many gamut mapping algorithms proposed. The things that I checked into Chromium (the polyhedral thing) were just expedient placeholders. I want to make sure there's agreement about where gamut mapping would be applied. If we have agreement there, then I'm sure we can find something reasonable. I'm going to be unavailable here for at least the next week. -- GitHub Notification of comment by ccameron-chromium Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9449#issuecomment-1984844613 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 8 March 2024 00:37:21 UTC