Re: [csswg-drafts] [css-color] Resolving color-mix() / color-contrast() (#7302)

The CSS Working Group just discussed `css-color] Resolving color-mix() / color-contrast()`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: css-color] Resolving color-mix() / color-contrast()<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/7302<br>
&lt;chris> People should also have https://github.com/w3c/csswg-drafts/issues/6168 open as they cover basically the same thing<br>
&lt;dael> chris: 7302 is about resolving color-mix and color-contrast. Have spec text but didn't say how to resolve<br>
&lt;dael> chris: Have another issue that talks about same thing. I'll copy discussion to both<br>
&lt;dael> chris: Suggested wording, emilio said it's slightly wrong and I agree. There is prop wording in color 5<br>
&lt;dael> chris: lea did a little codepen that implt color-mix so you can see how it works and get calc<br>
&lt;dael> chris: Useful to see what's happening, particularly when currentColor involved.<br>
&lt;dael> chris: If we can agree here I'll put this in the spec<br>
&lt;dael> chris: Color-mix has to inferit in as the whole thing<br>
&lt;chris> https://codepen.io/svgeesus/pen/QWQrQqr<br>
&lt;dael> jensimmons: codepen URL? I don't see it in the issue<br>
&lt;fantasai> +1 to computing currentColor components to themselves<br>
&lt;fantasai> even if that requires maintaining notations through inheritance<br>
&lt;dael> chris: It's in the other issue; discussion is happening in both<br>
&lt;dael> chris: I put in concrete wording. emilio pointed out it's a bit wrong, but other then that do people like the wording?<br>
&lt;dael> chris: smfr or jensimmons do you know what Sam is thinking?<br>
&lt;dael> smfr: Not sure I do. Can you give prop wording comment?<br>
&lt;chris> https://drafts.csswg.org/css-color-5/#resolving-color-values<br>
&lt;dael> chris: Dropping a link<br>
&lt;dael> chris: emilio didn't like the section being called resolving color values and I asked him about that. Didn't hear back yet. That's what it's named in color 4<br>
&lt;dael> fantasai: Call it computing color values?<br>
&lt;dael> chris: Resolving makes it sound used. This is both computed and used value<br>
&lt;dael> fantasai: I don't know what to do. It's fine then.<br>
&lt;dael> chris: It's different if currentColor is involved. In WK this is at parse time and WK doesn't do currentColor b/c it didn't know what to do. I suspect WK will need to change<br>
&lt;dael> fantasai: If I understand intention, it's that you compute the winning color and that becomes computed. If currentColor is used you compute individual values but don't resolve until used value time<br>
&lt;dael> fantasai: That makes sense. Not exactly what you wrote but if that's what you're going for good<br>
&lt;dael> fantasai: You wrote another sentence about resolving the used value to compute...confusing.<br>
&lt;dael> chris: That is intent. used is the winning color for contrast and the mix value for mix<br>
&lt;dael> fantasai: used is always a color. current is not always for currentColor<br>
&lt;dael> chris: Yes.<br>
&lt;fantasai> s/current is/computed is/<br>
&lt;dael> chris: Other thing is emilio opened an issue a while ago that if we resolve another bug happy to ship. bug closed today so I take as happyt o ship from Moz. Want to know if WK is happy to ship too<br>
&lt;dael> chris: Both browsers you have to run with flag enabled to get riht result so all tests flag<br>
&lt;dael> smfr: I think with WPT it runs with flags enabled<br>
&lt;dael> jensimmons: I think it enables for chrome and firefox but not safari<br>
&lt;dael> smfr: May want to fix currentColor before shipping on by default<br>
&lt;dael> chris: But sounds near-term thing on what spec should say?<br>
&lt;dael> fantasai: Seems like we should fix up spec to say what we want shipped and once that's ready we say go ahead<br>
&lt;dael> Rossen_: Do you want to go back and do that and let us know once ready<br>
&lt;dael> chris: Have to assume that's done to cover item 3 on agenda<br>
&lt;dael> Rossen_: We can resolve to accept text that is not quite correct. Let's consider the request once more next week and we can go from there<br>
&lt;dael> chris: Okay<br>
</details>


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


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

Received on Wednesday, 1 June 2022 23:21:38 UTC