Re: [csswg-drafts] Interpolate values between breakpoints (#6245)

The CSS Working Group just discussed `Interpolate values between breakpoints`, and agreed to the following:

* `RESOLVED: Rename the interpolation functions to *-interpolate()`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> TabAtkins: we talked about this a few weeks ago. people liked -mix(), but not -map() or -scale()<br>
&lt;TabAtkins> lea: linked, we talked about interpolate, tween, range, scale<br>
&lt;TabAtkins> lea: we're looking for somethign that works for many types<br>
&lt;TabAtkins> lea: color-sacle is fine, calc-scale is fine, but image-scale is bad, and generic scale() conflicts with transforms<br>
&lt;TabAtkins> lea: i think tween() is obscure and tied to animations<br>
&lt;TabAtkins> lea: range() sounds like it returns a range<br>
&lt;TabAtkins> lea: intermediate() is as longa s interpolate().<br>
&lt;TabAtkins> lea: interpolate() is clearest, it's just long. but other than that i think it's best option<br>
&lt;oriol> q+<br>
&lt;TabAtkins> lea: so if we can't do scale() i think interpolate() is best<br>
&lt;TabAtkins> lea: confusing is worth than long<br>
&lt;kbabbitt> q+<br>
&lt;astearns> ack oriol<br>
&lt;TabAtkins> oriol: i had a minor question of what's different between mix() and interpolate()<br>
&lt;lea> TabAtkins: The mix functions do a weighted average, the interpolate functions take a sequence of values and an input value, like a gradient, and give you where your progress position landed on<br>
&lt;astearns> ack kbabbitt<br>
&lt;lea> e.g. `color-scale(30%, white, red 30%, black)` would give you red<br>
&lt;TabAtkins> kbabbitt: i like the name interpolate(). agree it's long but it's used elsewhere<br>
&lt;TabAtkins> kbabbitt: bramus pointed out we use it in color-interopolation and interpolate-size<br>
&lt;astearns> ack dbaron<br>
&lt;TabAtkins> kbabbitt: i agree clear is more important than short<br>
&lt;TabAtkins> dbaron: another idea is use the word tab just said, gradient()<br>
&lt;TabAtkins> dbaron: that's a thing people currently understand<br>
&lt;TabAtkins> TabAtkins: i think color-gradient() is a little funky<br>
&lt;dbaron> s/another idea/another idea (maybe a bad idea, but worth considering)/<br>
&lt;TabAtkins> astearns: have there been any arguments against interpolate() besides length?<br>
&lt;TabAtkins> TabAtkins: no<br>
&lt;ntim> gradient reminds me of math gradient descent<br>
&lt;oriol> q+<br>
&lt;astearns> ack oriol<br>
&lt;TabAtkins> oriol: a shorter idea, pick()?<br>
&lt;lea> `image-pick()`, `color-pick()`, `calc-pick()`<br>
&lt;lea> TabAtkins: My only worry is that it sounds like you're picking one of existing options, not interpolating<br>
&lt;TabAtkins> TabAtkins: we can just go for interpolate()<br>
&lt;TabAtkins> lea: yeah i think anything else is just unclear. saving a fe wmore characters isn't worth it<br>
&lt;TabAtkins> astearns: anyone who would prefer not to resolve on interpoltae() today?<br>
&lt;TabAtkins> ntim: what's the sytnax of this function?<br>
&lt;TabAtkins> TabAtkins: [summarizing] it's basically the linear-gradient() syntax, more or less<br>
&lt;TabAtkins> astearns: objectiosn to using interpolate()?<br>
&lt;TabAtkins> RESOLVED: Rename the interpolation functions to *-interpolate()<br>
&lt;TabAtkins> lea: is it before or after the type particle in the name?<br>
&lt;TabAtkins> TabAtkins: after, like color-mix()<br>
&lt;bramus> Yay!<br>
&lt;TabAtkins> astearns: but if yo uwant the other way, open an issue<br>
</details>


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


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

Received on Thursday, 3 April 2025 15:45:46 UTC