Re: [csswg-drafts] [css-color-4] `rgba()` is legacy so does not support `none`. Right? (#7900)

The CSS Working Group just discussed ``[css-color-4] `rgba()` is legacy so does not support `none`. Right?``, and agreed to the following:

* `RESOLVED: non-RCS rgb() and hsl() can mix numbers/%s when using the modern syntax (space and slash, not comma).`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> chris: We have an old syntax which has commas for everything<br>
&lt;TabAtkins> chris: And a new which is space and slash<br>
&lt;astearns> ack chris<br>
&lt;TabAtkins> chris: We've added a bunch to that new syntax, like RCS<br>
&lt;TabAtkins> chris: But it used to be that everything had to be a % or everything a number, that's from CSS1<br>
&lt;TabAtkins> chris: In RCS you can mix them tho<br>
&lt;TabAtkins> chris: My proposal is that the modern syntax, only, allows mixing %s and numbers.<br>
&lt;TabAtkins> chris: Also the modern syntax can use 'none'. I'd also like to keep that restricted to the modern syntax.<br>
&lt;TabAtkins> chris: We have very good interop on what's currently specified<br>
&lt;TabAtkins> chris: People have argued that for clarity we should extend the capabilities to all syntaxes, but I think it's a bad idea - we have very solid interop as-is.<br>
&lt;TabAtkins> I'm totally fine with this.<br>
&lt;TabAtkins> chris: So proposed reoslution is we backport mixing number/% to the modern syntax of non-RCS rgb() and hsl()<br>
&lt;argyle> +1<br>
&lt;TabAtkins> astearns: Questions?<br>
&lt;TabAtkins> astearns: I assume this is okay with the issue commenters?<br>
&lt;TabAtkins> chris: There's one in the thread who had several suggestions but no strong opinion. Other than that, agreement in the thread.<br>
&lt;TabAtkins> RESOLVED: non-RCS rgb() and hsl() can mix numbers/%s when using the modern syntax (space and slash, not comma).<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7900#issuecomment-1423013714 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 8 February 2023 17:50:47 UTC