- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Dec 2021 20:37:26 +0000
- To: public-css-archive@w3.org
I agree this is under-specified and confusing. I suspect the language you quote was not updated when we went to extended colorspaces for all the predefined RGB spaces. `hsl` and `hwb` certainly are unable to express out of gamut colors, so in those cases certainly gamut mapping would occur. And doing manipulations in `hsl` is likely to be common as people move color-manipulation logic from the likes of Sass where hsl was until recently the only option. > Should the color(display-p3 0 1 0) color be gamut mapped to the sRGB gamut, or would it be ok for this to produce a result like color(srgb -5.35 10.17 -3.43)? Well ideally it would produce `color(srgb -0.5116 1.01827 -0.3107)` :) but yes, there is color space conversion but no gamut mapping in this case CSS Color 4 [says](https://drafts.csswg.org/css-color-4/#interpolation-space), in Color Spaces for Interpolation: > If the colors to be interpolated are outside the gamut of the interpolation space, then once converted to that space, they will contain out of range values. > These are not clipped, but the values are interpolated as-is. I think the fix is to change the text you cited, from "has a smaller gamut" to "cannot express the color" plus adding an example. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6913#issuecomment-1002768193 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 29 December 2021 20:37:27 UTC