- From: Eric Portis via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Jun 2024 23:31:08 +0000
- To: public-css-archive@w3.org
@tabatkins: > (2) We propose that, when mapping a used color into the monitor gamut, by default it is done by naive r/g/b channel clipping, to match existing image/video gamut reduction behavior. Clipping Rec.2020 colors to, e.g., sRGB sometimes produces significant lightness shifts vs doing what's in the spec now (which tries to preserve lightness above all else). Here's a ~worst-case, real-world example of how different results can be, even post-mapping-to-Rec.2020: https://codepen.io/eeeps/pen/zYQPqKM @LeaVerou: > I think it's quite important to give authors control of what to prioritize: hue, chroma, lightness, relationships between colors, etc. since use cases have drastically different demands. For accessibility, I think preserving lightness should probably be the default. I agree; "match the image processing pipeline" should be an option, but I would prefer if "preserve lightness" were the default – not only for the proposed first stage, where wildly out-of-gamut OkLCH colors are mapped to Rec.2020, but also when doing the proposed second stage: mapping Rec.2020 colors to physical display gamuts. -- GitHub Notification of comment by eeeps Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9449#issuecomment-2164062188 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 June 2024 23:31:09 UTC