- From: Jeffrey Yasskin via GitHub <noreply@w3.org>
- Date: Wed, 04 Jun 2025 22:20:48 +0000
- To: public-css-archive@w3.org
I think the ball's in the WG's court to pick an algorithm to map from the device-independent (non-RGB) spaces to Rec.2020 (or a '"nicer-shaped" surface very close to the Rec2020 gamut'). Chris C opened #10579 to help that happen, but there's been no progress on that issue, aside from Chris C saying he's happy with all the options that have been proposed in that issue. Once the WG settles on an algorithm, it looks like Chris C is happy to implement it, given the permission to then clip from Rec.2020 to the user's display. I see some discussion after https://github.com/w3c/csswg-drafts/issues/9449#issuecomment-2162711081 that questions the [resolution](https://github.com/w3c/csswg-drafts/issues/9449#issuecomment-2162711081) to allow clipping from Rec.2020 to the user's display. My understanding is that this level of implementation freedom is a hard requirement from all of the browser engines, and that if folks want to fix the problem for wildly out-of-gamut colors, they should focus on the part that Chris C has expressed flexibility on. -- GitHub Notification of comment by jyasskin Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9449#issuecomment-2941751249 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 4 June 2025 22:20:49 UTC