Re: [csswg-drafts] [css-values-4] min/max(%, %) should explicitly evaluate against the % value, not the resolved value (#4227)

The CSS Working Group just discussed `[css-values-4] min/max(%, %) should explicitly evaluate against the % value, not the resolved value`, and agreed to the following:

* `RESOLVED: Close no change`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-values-4] min/max(%, %) should explicitly evaluate against the % value, not the resolved value<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4227<br>
&lt;dael> TabAtkins: Curious who added this<br>
&lt;dael> astearns: Gerard<br>
&lt;dael> TabAtkins: I think we have this resolved in spec. Let's confirm<br>
&lt;dael> TabAtkins: Question about what to do with compare functions when you have less then obv value like %. min of 50% and 10%. Depending on context 50% could be the smaller when it's a negative value<br>
&lt;bradk> I wish we could also go the other way, and get the accent color for use in other things, such as with ‘env(accent-color)’<br>
&lt;dael> TabAtkins: Extra confusing when you mix % and no-%. You can't figure out until you resolve to lengths.<br>
&lt;dael> TabAtkins: Want to make sure everyone is cool with spec rules that you resolve as much as you can at each step but % can't be resolved at computed value time unless they are a terminal type for the property. If lengths have to wait.<br>
&lt;bradk> OK. Sorry, I came in late<br>
&lt;dael> TabAtkins: If that's okay, great. I don't think we need a resolution unless ou think we should.<br>
&lt;dael> astearns: I suspect Gerard would like a resolution so he can finish tests<br>
&lt;dael> astearns: Any concerns with the spec text?<br>
&lt;leaverou> florian bradk astearns: I filed the issue: https://github.com/w3c/csswg-drafts/issues/5900<br>
&lt;dael> astearns: Prop: Close no change<br>
&lt;dael> 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/4227#issuecomment-768453578 using your GitHub account


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

Received on Wednesday, 27 January 2021 17:38:55 UTC