Re: [csswg-drafts] [css-color-4] a new property to limit to a specific color gamut (#10038)

`none` is different than `clip`, I think. `none` would tell the user agent to leave the color as is, outside of the display gamut, essentially leaving it up to the display hardware (or whatever graphics API the user agent is interacting with) to clip, do its own gamut mapping, or error in some way.

I think we would need multiple values, with some shorthands. Essentially, we are defining a path to a color that can be displayed on a user's device, so we need `method destination gamut, method destination gamut, ...`. 

For instance-

- `auto rec2020, clip` would use default GMA to map to rec2020, and then clip to the device as needed.
- `clip p3` would clip to p3.
- `clip rec2020, auto p3, clip srgb` could be possible, clipping to rec2020, then default GMA to p3, then clip to srgb. 
- `auto device clip srgb` would use the default GMA to get to the device gamut, and then do an additional clipping to srgb
- `auto device` could be the default (and approximate current specified behavior), would use the current CSS GMA to map to the device gamut

Instead of `clip` and `auto`, it could be useful to have intent-based names, for instance `preserve-contrast` instead of auto and `preserve-chroma` instead of `clip`?

This does raise the burden on implementers to implement multiple algorithms, mapping to multiple gamuts.

-- 
GitHub Notification of comment by jamesnw
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10038#issuecomment-2012216279 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 21 March 2024 12:55:59 UTC