- From: Christopher Cameron via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Aug 2022 17:29:25 +0000
- To: public-css-archive@w3.org
> It is far more important to get a color closer to the author intent (@svgeesus [demonstrated above](https://github.com/w3c/csswg-drafts/issues/7610#issuecomment-1219663823) what kind of poor results clipping produces), rather than to accommodate the odd case where the same CSS color is displayed next to the same canvas color. This is a case from a partner, developing a graphic design application. The main work area is a low latency WebGL canvas in P3 (pushed to a hardware overlay whenever possible), and they have a color picker tool that is CSS. Another example is a logo that is represented as an image, and the content author wants text on the page to match the logo's color. This is also something that users have been able to do forever with sRGB images. If an image is sRGB, then specifying that exact same pixel value as a CSS color has always produced an identical color. I don't think we should sweep away that functionality. With respect to author intent, I've elaborated on the above example with [this test page](https://ccameron-chromium.github.io/gamut-map/gamut-map/red-redder.html) here. - on a P3 display, we get [this image](https://raw.githubusercontent.com/ccameron-chromium/gamut-map/main/gamut-map/rr-p3.png), where "redder?" is more saturated - on an sRGB display today, we get [this image](https://raw.githubusercontent.com/ccameron-chromium/gamut-map/main/gamut-map/rr-srgb-no-gamut-map.png), where there is no difference - on an sRGB display with gamut mapping, we get [this image](https://raw.githubusercontent.com/ccameron-chromium/gamut-map/main/gamut-map/rr-srgb-gamut-mapped.png), where "redder?" is less saturated -- GitHub Notification of comment by ccameron-chromium Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7610#issuecomment-1226026465 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 August 2022 17:29:27 UTC