Re: [csswg-drafts] [css-color-5] Make all color components in Relative Color Syntax optional (#6938)

The CSS Working Group just discussed `CSS Color 5: Relative Color Syntax optional components`, and agreed to the following:

* `RESOLVED: Close no change`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: CSS Color 5: Relative Color Syntax optional components<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/6938<br>
&lt;fantasai> lea: Right now have a relative color syntax that allows you to do arbitrary math over components of a single color<br>
&lt;fantasai> lea: also converts the color you're working with to the color space you're using<br>
&lt;fantasai> lea: could just want to convert to the color space<br>
&lt;fantasai> lea: e.g. from-color l c h<br>
&lt;fantasai> lea: can also convert using color-mix() and 100% of the color you want<br>
&lt;fantasai> lea: Chris and I were thinking this is awkward<br>
&lt;chris> q+<br>
&lt;fantasai> lea: maybe just allow drop the components to convert spaces<br>
&lt;fantasai> lea: and if 3 or zero components, then maybe could even have some components<br>
&lt;fantasai> lea: but Tab seems a bit against that<br>
&lt;fantasai> lea: QUestion of why convert among spaces if not doing anything with it<br>
&lt;fantasai> lea: ...<br>
&lt;fantasai> lea: right now adding to all features that use interpolation<br>
&lt;fantasai> lea: if no reason, then not worht having a shortcut<br>
&lt;fantasai> lea: Chris, any reason to convert color spaces but not do anything with the resulting color?<br>
&lt;fantasai> chris: if we do make thse optional, then I would want to make all components optional<br>
&lt;fantasai> chris: or maybe trailing ones, is sort of annoying<br>
&lt;fantasai> chris: that's confusing. I'd prefer all or none<br>
&lt;fantasai> chris: but don't see point for using positional ordering<br>
&lt;fantasai> lea: what's use case for none of them?<br>
&lt;dino> ack dino<br>
&lt;fantasai> chris: the use case was color space so I can mess around with it, but now we have color-extract()<br>
&lt;fantasai> lea: even with relative color syntax could do color conversion and do math on the componetns<br>
&lt;fantasai> lea: so I'm not sure why you would need to do that, so inclined to close this as no change<br>
&lt;fantasai> chris: I think that would be fine<br>
&lt;fantasai> Rossen_: can we do that?<br>
&lt;fantasai> lea: yes, that's my proposal. Unless Chris can think of a use case for it<br>
&lt;fantasai> Rossen_: we can always re-open if a strong use case comes forward<br>
&lt;fantasai> RESOLVED: Close no change<br>
</details>


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


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

Received on Wednesday, 12 January 2022 18:01:10 UTC