- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Feb 2023 23:50:15 +0000
- To: public-css-archive@w3.org
> This value round trips fine using the algorithm in 7.1, with some float-precision issues. > [Here's a demo for arbitrary values for display-p3 input, including HWB](https://jsfiddle.net/zn6uhgj7/1/). All resulting values for hsl make sense if we allow saturation > 100%. Interesting. I don't recall why I thought the values became nonsensical; I would need to look again. If HSL and HWB were made unbounded, we would need to drop statements [like this](https://drafts.csswg.org/css-color-4/#the-hsl-notation): > If the saturation or lightness are less than 0% or greater than 100%, they are clamped to those values at parsed-value time, before being converted to an sRGB color. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8444#issuecomment-1444740674 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 24 February 2023 23:50:17 UTC