- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 Feb 2023 22:51:44 +0000
- To: public-css-archive@w3.org
> The crux of the confusion are [these tests](https://github.com/web-platform-tests/wpt/blob/2bb60461aad0075ca8e1ae08aa836f06b4870d49/css/css-color/parsing/gamut-mapping.html), which, if I understand correctly are an instance of a) and not b)? They are c) Not expressible in a given color format. HSL and HWB require in-gamut sRGB values as input, and give nonsense values if they get negative number or numbers grester than 100%. So, as the spec says, they need gamut mapped before the sRGB to HSL/HWB conversion step. So (unlike gamut mapping to the used value on the display) this case is observable through script, and the tests are indeed valid. Used values are not exposed through script, the only way to see if the right color is being displayed is to physically measure it or compare it visually to a reference color patch. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8444#issuecomment-1439195271 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 21 February 2023 22:51:45 UTC