- From: Christopher Cameron via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Aug 2022 16:33:49 +0000
- To: public-css-archive@w3.org
> Given how trivially easy it is to specify out of gamut colors with e.g. LCH or OKLCH, having to do manual gamut mapping to not get a terrible result is **completely** unacceptable. Not to mention that the `color-gamut` media query is a very blunt instrument for this purpose. > > I think there is a fundamental misunderstanding permeating this discussion. Going out of gamut is not some edge case we can relegate to script or manual computation, it will be very very common once authors can specify wide gamut colors, so it's important to handle it well and not sweep it under the rug. Yes, this highlights an important issue. Should someone creating content specify colors (significantly) outside of the capabilities of the device on which they are authoring content? Encouraging that strikes me as a bad idea -- the author is making content without knowing what it actually looks like. Just in the above example, the color(p3 1 0 0) gamut-mapped to sRGB looks is less-saturated than srgb(1 0 0), which is the opposite of what actually happens when it is rendered on an a P3 display. The parameterization and interpolation of LCH is highly desirable. The ability to swing wildly out of gamut isn't. What about the following compromise: take away LCH, and replace it with something like LCH-P3, with gamut mapping to P3 baked in? -- GitHub Notification of comment by ccameron-chromium Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7610#issuecomment-1225965068 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:33:51 UTC