- From: Christopher Cameron via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Aug 2022 16:12:12 +0000
- To: public-css-archive@w3.org
> I want to get back to the color matching issue, and take the image part out of the equation. > > Consider the following 3 pieces of web content: > > * A div which uses `color(display-p3 1 0 0)` as the background > * A 2D canvas in `display-p3` in which solid `color(display-p3 1 0 0)` is drawn > * A WebGL canvas in `display-p3` which is cleared to the color (1, 0, 0, 1) > > Should these appear the same when displayed on a device that has a gamut that is, say, halfway between sRGB and P3? If not, why not? > > If a content author wants to display something that part-div, part-2D-canvas, and part-WebGL, should it be possible for the author to color-match between these elements, so that there are no seams in their content, or not? I went ahead and wrote up an example of the behavior where gamut mapping is applied only to CSS colors, but not images and canvases. Consider [this page](https://ccameron-chromium.github.io/gamut-map/gamut-map/color-match.html), which has a canvas, a CSS color, and an image. - If displayed on a P3 device, the result will be [this image](https://raw.githubusercontent.com/ccameron-chromium/gamut-map/main/gamut-map/p3-original.png). - When displayed on an sRGB device, without gamut mapping, the result will be [this image](https://raw.githubusercontent.com/ccameron-chromium/gamut-map/main/gamut-map/srgb-clipped.png) - When displayed on an sRGB device, with gamut mapping enabled, the result will be [this image](https://raw.githubusercontent.com/ccameron-chromium/gamut-map/main/gamut-map/srgb-gamut-mapped.png) This uses the gamut mapping math in [this notebook](https://colab.research.google.com/drive/1GogK3_KPULEiproupphWtTlSlQZVtqZk?usp=sharing). Is this above characterization correct? -- GitHub Notification of comment by ccameron-chromium Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7610#issuecomment-1225938386 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 16:12:14 UTC