- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Sat, 01 Jul 2023 11:40:00 +0000
- To: public-css-archive@w3.org
No, it looks like just a failure on my part to update all affected parts of the spec. [This edit](https://github.com/w3c/csswg-drafts/commit/4f09d0500a5fe768c4fadd032942b220d017a105) changed `They are <<number>>s or <<percentage>>s` to `They are <<number>>s` but only for relative `color()` not for other color functions. You are right that `hsl()` and `hwb()` [were changed to always allow number or percentage](https://github.com/w3c/csswg-drafts/commit/b5fdc892cc1cf10e2b6484eb10e93ed1e9aa7dca), and the [CSS WG resolution](https://github.com/w3c/csswg-drafts/issues/7876#issuecomment-1379264467) was that channel keywords should resolve to `<number>`. * RESOLVED: keywords with multiple specified types result in number @tabatkins had [pointed out that channel keywords were still using percentage for HWB](https://github.com/w3c/csswg-drafts/issues/7876#issuecomment-1379197254), and I [stated that this was correct](https://github.com/w3c/csswg-drafts/issues/7876#issuecomment-1379222327) because that predated the resolution (which was [made on the call that same day](https://github.com/w3c/csswg-drafts/issues/7876#issuecomment-1379264467)). And the spec was even changed elsewhere to refer to these being number for HSL and HWB, see [this edit[(https://github.com/w3c/csswg-drafts/commit/9f319804bf6ac8fec705978acedec44cac961266), as part of https://github.com/w3c/csswg-drafts/issues/8322. So I should fix that, for consistency. Thanks for your careful review! -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9016#issuecomment-1615864082 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 1 July 2023 11:40:01 UTC