- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Feb 2023 20:10:28 +0000
- To: public-css-archive@w3.org
> > For what it is worth, Chrome supports none in all 4 syntaxes. > > It does? No. I apologize. > I'm a lot less convinced that allowing legacy, comma-based syntaxes to accept 'none' (and RCS??) would be a good idea. Although having re-read this and related issues for the n th time, I'm also not sure if that is actually being proposed. I proposed it, as well as accepting them only in modern `rgb()`/`hsl()`. But I have no strong opinion. I came across [this usage data](https://almanac.httparchive.org/en/2022/css#colors) a few days ago (referenced in this [guide](https://developer.chrome.com/articles/high-definition-css-color-guide/)). I was surprised to see `rgba()` and `hsla()` more often used than `rgb()` and `hsl()`. I would have been interested to know if authors are more often using legacy or modern syntax. Anyway, authors using the legacy syntax would now have to switch to the modern syntax in order to use `none` and RCS. -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7900#issuecomment-1421377947 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 February 2023 20:10:30 UTC