Re: [csswg-drafts] [css-color-5] Clarification on how `channel keywords` with multiple specified types work (#7876)

The CSS Working Group just discussed `channel keywords`, and agreed to the following:

* `RESOLVED: keywords with multiple specified types result in number`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: channel keywords<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/7876<br>
&lt;fantasai> chris: main issue raised was that the keywords could have two possible types, doesn't work<br>
&lt;fantasai> chris: either number or percentage<br>
&lt;fantasai> chris: went with number to be consistent with serialization<br>
&lt;fantasai> TabAtkins: nit, you accidentaly did percentage for wmb, but otherwise it's great<br>
&lt;fantasai> chris: It's because color-4 it only takes a percentage<br>
&lt;fantasai> TabAtkins: Ah, in that case it's completely fine<br>
&lt;fantasai> chris: any other comments?<br>
&lt;fantasai> chris: anyone need more time?<br>
&lt;fantasai> ntim: didn't have a chance to look at it<br>
&lt;fantasai> lea: does that mean for rgb they resolve to 0-255 range?<br>
&lt;fantasai> chris: yes, but remember it's 0.0 to 255.0 so you don't lose precision<br>
&lt;fantasai> lea: but inconsistent with rgb models<br>
&lt;fantasai> chris: because it was invented poorly<br>
&lt;fantasai> lea: I agree but does that mean we don't need relative color syntax for rgb?<br>
&lt;Rossen_> q?<br>
&lt;fantasai> chris: I have a lot of trouble coming up with use cases<br>
&lt;Rossen_> ack ntim<br>
&lt;fantasai> chris: I haven't found a good example<br>
&lt;fantasai> lea: I think it's primarily for ocmpletenes, but maybe we should not do it just for completeness<br>
&lt;fantasai> lea: restrict to color()?<br>
&lt;fantasai> chris: I wouldn't go that far<br>
&lt;fantasai> chris: let's resolve this and deal in other issues?<br>
&lt;fantasai> chris: get consensus on going to number?<br>
&lt;fantasai> Rossen_: So do we have enough consensus?<br>
&lt;lea> s/ocmpletenes, but maybe we should not do it/completeness, but we don't generally do things/<br>
&lt;fantasai> lea: consensus is about every component that's "number or something else" resolves to number?<br>
&lt;fantasai> lea: so hues resolve to numbers?<br>
&lt;fantasai> chris: yeah, all examples treat hues as number<br>
&lt;fantasai> chris: so I think most ppl are treating as numbers<br>
&lt;fantasai> lea: yes, that's what authors do<br>
&lt;fantasai> [...]<br>
&lt;argyle> +1 to number<br>
&lt;fantasai> chris: Proposal, keywords with multiple specified types result in number<br>
&lt;fantasai> Rossen_: Any additional feedback or objections?<br>
&lt;fantasai> jensimmons: this is fine with us from Apple<br>
&lt;fantasai> RESOLVED: keywords with multiple specified types result in number<br>
</details>


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


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

Received on Wednesday, 11 January 2023 17:49:42 UTC