Re: [csswg-drafts] [MQ] color-gamut Keywords (#4535)

The CSS Working Group just discussed `[MQ] color-gamut Keywords`, and agreed to the following:

* `RESOLVED: Remove Hyphen from rec2020 in all context; everything else stays as is`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [MQ] color-gamut Keywords<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4535<br>
&lt;dael> astearns: chris you commented last<br>
&lt;dael> chris: I'm of the opinion this is shipped in 2 browsers so large change cost. If we designed now more generic names would be better but fact is Apple and others have shipped P3-gamut.<br>
&lt;dael> chris: We discussed hyphenation and got consensus on that and I don't want to rename them back. We went to display-P3 and then we'd have to rename and it would become ambig again. TabAtkins has a different opinion that they mean the same. I don't think they do mean the same<br>
&lt;dael> TabAtkins: I said they are approx the same. They're close to meaning same. Especially in ref2020 where one is a hypen and one not is extremely bad. p3 and display-p3 are different words.<br>
&lt;fantasai> s/is a hypen/has a hyphen/<br>
&lt;dael> TabAtkins: Still of opinion we should be consistent. We shouldn't change color gamut so we should revert color function keywords because else people will ask why different<br>
&lt;dael> florian: I would argue mean the same. If you understand MQ to ask if gamut is supported by screen with this approx as large as this color space then it's yes. If screen isn't an exact match it's okay. You're not asking about color space specifically<br>
&lt;dael> chris: No one suggests renamining display-P3 to P3?<br>
&lt;dael> TabAtkins: I'm possibly in that relm. I would like ref2020 to be consistently hyphenless. P3 and display-P3 sound different. Hyphen diff shoudln't be<br>
&lt;dael> florian: I would align P3 to the one used in MQ.<br>
&lt;dael> chris: Remember Apple wanted display-P3. When we reverted to what they wanted and what everyone talks about that's the name<br>
&lt;dael> TabAtkins: That's why I'm okay with display-P3. A subset of name in color gamut is okay. P3 means approx any of these.<br>
&lt;dael> florian: I don't think I would object to different P3. But your question was anyone suggesting we merge and I suggest we do. Won't object to don't<br>
&lt;dael> TabAtkins: Revert ref2020 in color to be hyphenless and leave p3/display-p3 alone?<br>
&lt;dael> chris: Okay with that....<br>
&lt;fantasai> I would strongly object to having the only difference be the presence of hyphens<br>
&lt;dael> florian: Maybe hear from Apple?<br>
&lt;dael> smfr: Apple prefer to keep<br>
&lt;dael> astearns: Prop: Remove Hyphen from ref2020?<br>
&lt;dael> astearns: Objections?<br>
&lt;smfr> s/ref2020/rec2020/<br>
&lt;chris> s/ref/rec/<br>
&lt;dael> RESOLVED: Remove Hyphen from rec2020 in all context; everything else stays as is<br>
</details>


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

Received on Wednesday, 15 January 2020 17:11:03 UTC