- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Sep 2021 15:38:27 +0000
- To: public-css-archive@w3.org
There is some better wording in [Specifying profiled colors: the color(https://drafts.csswg.org/css-color-4/#color-function) function](): > For custom color spaces, specified component values less than 0 or 0%, or greater than 1 or 100% are not invalid; they are clamped to the valid range at computed value time. This is because ICC profiles typically do not accept out of range input values. > For predefined color spaces, specified component values less than 0 or 0%, or greater than 1 or 100% are not invalid; these out of gamut colors are gamut mapped to the valid range at computed value time, with a relative colorimetric intent. Which contradicts the > with each having a valid range of [0, 1]. in the definition of `sRGB`, `display-p3` etc. And these are all in the `color()` function so unafected by legacy deadweight. It looks like those could simply be reworded. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6087#issuecomment-929346609 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 28 September 2021 15:38:29 UTC