- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Feb 2023 15:26:40 +0000
- To: public-css-archive@w3.org
I am sorry to open discussions in different issues that are all related to back-porting mixed `<number>` and `<percentage>` to CSS Color 4, but this issue seems definitely appropriate for asking the following questions. Can you please clarify the range to resolve `<percentage>` to `<number>` when it represents saturation/lightness in `hsl()` and `hsla()`? 0% resolves to 0 and 100% to 1? Chrome/FF do not support `<number>` for these components, as expected by [WPT](https://github.com/web-platform-tests/wpt/blob/b823b2fa1f3e9779f947403e537c47dc5b5e8586/css/css-color/parsing/color-valid-hsl.html). You did not back-ported mixing `<number>` and `<percentage>` in `hwb()`. I do not know if this was intentional but the same question applies to resolve `<percentage>`, which is allowed in CSS Color 5. But I am off topic here... so let's continue! =) > 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 seems to enforce `<percentage>` to resolve in [0,1] for custom color profiles, whereas `<percentage>` resolves to different ranges in other color functions, depending on the component. I may have missed how to resolve `<percentage>` in CSS Color 5, when the target range is not defined in CSS Color 4. Otherwise, this question can be discussed in a separate issue, if you prefer. -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8322#issuecomment-1440253903 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 February 2023 15:26:42 UTC