Re: [csswg-drafts] [css-values] Clarification on Simplification for clamp() with none values (#13535)

The CSS Working Group just discussed `[css-values] Clarification on Simplification for clamp() with none values`, and agreed to the following:

* `RESOLVED: when possible we simplify clamp() to min() or max()`

<details><summary>The full IRC log of that discussion</summary>
&lt;ydaniv> TabAtkins: currently the spec for clamp() says it acts like a max/min depending on where you use the value<br>
&lt;ydaniv> ... [summarizing description]<br>
&lt;romain> q+<br>
&lt;ydaniv> ... per spec Chrome is wrong, doesn't matter much to me how we go on with this<br>
&lt;astearns> ack romain<br>
&lt;emilio> q+<br>
&lt;ydaniv> ... unless anybody has a reason to care about that behavior specifically, I suggest open a bug on Chrome and close no change<br>
&lt;ydaniv> romain: How does this interact with color interpolation, like color-mix where we also have none, where this can be simplified or not<br>
&lt;ydaniv> ...<br>
&lt;ydaniv> TabAtkins: those nones are unrelated keywords, so should not have any effect<br>
&lt;ydaniv> romain: I think lea had some note regarding that<br>
&lt;ydaniv> ... where substituting none in color function is not the same<br>
&lt;ydaniv> TabAtkins: you can not write none into a claculation<br>
&lt;ydaniv> ... so doesn't have any connection with this none, it's not part of calculation, this none is only related as value to clamp()<br>
&lt;ydaniv> ... so it can't sub-in for that<br>
&lt;ydaniv> romain: ok, thanks<br>
&lt;astearns> ack emilio<br>
&lt;ydaniv> emilio: I don't care which way, but in FF it is implemented and was easier to implement.<br>
&lt;ydaniv> ... I'm ok with no change, it's a bit weird, FF actually does the same thing as Chrome but we did not ship it yet<br>
&lt;ydaniv> TabAtkins: so it's ok either way, don't care much<br>
&lt;ydaniv> emilio: my opinion is that it's simpler to implement with min/max<br>
&lt;ydaniv> astearns: is this an over simplification in any way?<br>
&lt;ydaniv> TabAtkins: no, you don't get one or the other, but it's the exact behavior<br>
&lt;ydaniv> ... we added the none since using clamp() as min/max is more handy<br>
&lt;ydaniv> astearns: don't see anyone from WebKit, we could resolve as a way to get their opinion<br>
&lt;emilio> sg<br>
&lt;ydaniv> TabAtkins: SGTM<br>
&lt;ydaniv> PROPOSED RESOLUTION: when possible we simplify clamp() to min() or max()<br>
&lt;ydaniv> astearns: objections?<br>
&lt;ydaniv> RESOLVED: when possible we simplify clamp() to min() or max()<br>
</details>


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


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

Received on Wednesday, 11 March 2026 15:14:57 UTC