W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2021

Re: [csswg-drafts] [css-animations][css-transitions][css-gradients] Higher level CSS interpolation module (#5617)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Tue, 27 Jul 2021 16:57:27 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-887675565-1627405046-sysbot+gh@w3.org>
The CSS Working Group just discussed `Higher level CSS interpolation module`, and agreed to the following:

* `RESOLVED: This is something we want to work on, exact details TBD`

<details><summary>The full IRC log of that discussion</summary>
&lt;emilio> topic: Higher level CSS interpolation module<br>
&lt;emilio> github: https://github.com/w3c/csswg-drafts/issues/5617<br>
&lt;emilio> astearns: this also might be covered in-spec but not impls<br>
&lt;emilio> ... in addition to using calc() across various types, they want to use easing functions for ~all properties<br>
&lt;chris> q+<br>
&lt;emilio> ... haven't looked at it in a while, but perhaps we can use easing functions in all properties or is it more limited than that?<br>
&lt;emilio> chris: when we added animations and before with SMIL we got some feedback from animators saying that it only worked on two values<br>
&lt;emilio> ... so this is a thing we want any time we transition, animate or interpolate<br>
&lt;Rossen_> ack chris<br>
&lt;chris> yes, done<br>
&lt;emilio> astearns: and I don't think we have any of the easing editors on the call<br>
&lt;emilio> ... it seems they are meant to be used anywhere where a value could be set<br>
&lt;emilio> fantasai: wdym with that?<br>
&lt;fantasai> https://www.w3.org/TR/css-easing-1/#easing-functions<br>
&lt;emilio> ... they are meant to be used where an easing function is asked for<br>
&lt;lea> q+<br>
&lt;emilio> ... it's a function, not a value<br>
&lt;emilio> astearns: I believe scott's ask is for things like optical sizing to be able to use easing functions as values<br>
&lt;chris> seems like a reasonable ask<br>
&lt;emilio> ... to be able to have more subtle transition across values<br>
&lt;emilio> fantasai: you need a range of values for that as well<br>
&lt;emilio> lea: if I'm reading this correctly, easing functions is just a minor piece of that issue<br>
&lt;miriam> q+<br>
&lt;emilio> ... there are other important issues like mixing relative units<br>
&lt;emilio> ... you need to do ?? manually in keyframes<br>
&lt;chris> s/??/spacing/<br>
&lt;emilio> ... I didn't open this issue and scott isn't here, but I think the idea is to unify all these interpolation mechanisms<br>
&lt;Rossen_> ack lea<br>
&lt;emilio> ... so that the same features are available everywhere<br>
&lt;Rossen_> ack miriam<br>
&lt;emilio> miriam: when interpolating between breakpoints wrt media/container queries, part of the complexity is that you have to set those breakpoints and then somehow attach an animation to those breakpoints<br>
&lt;emilio> ... I've thought a bit to scrolling animations and animation timelines linked to container / media queries<br>
&lt;argyle> q=+<br>
&lt;argyle> q+<br>
&lt;emilio> ... not sure if something like that would help<br>
&lt;Rossen_> ack argyle<br>
&lt;argyle> https://shadows.brumm.af/<br>
&lt;emilio> argyle: I use a lot of online tools that would generate things for me like shadows (^)<br>
&lt;emilio> ... what I'd like to do instead of something like this is letting CSS do this with a clamp-like function<br>
&lt;emilio> ... so that I can get an easing shadow with a natural curve<br>
&lt;emilio> ... it'd be really cool to pass curves to shadows / gradients / etc rather than a bunch of percentages<br>
&lt;emilio> ... almost anywhere where we accept multiple values we could shorten the entire stack into one or two by specifying the range and a curve<br>
&lt;emilio> ... if you're looking for use cases for stuff like this I can help<br>
&lt;emilio> astearns: I think this is very relevant, there are lots of use cases to express stuff in terms of curves of values. not quite sure where to start though<br>
&lt;emilio> Rossen_: where do we go from here? Is this the most appropriate issue to capture this?<br>
&lt;emilio> astearns: bkardell suggests this as an expansion to web-animations-2<br>
&lt;astearns> s/bkardell/birtles/<br>
&lt;fantasai> emilio: Use cases adam mentions aren't particularly animation-like<br>
&lt;emilio> Rossen_: shouldn't but it's where most that stuff is defined<br>
&lt;Rossen_> q?<br>
&lt;emilio> Rossen_: sounds like enough motivation was heard. There are some overlapping efforts in the interpolation space with animations-2, and if that's not enough we need to figure out what else is needed<br>
&lt;emilio> ... is there anything else we can do with this issue?<br>
&lt;lea> +1 to work on it<br>
&lt;emilio> RESOLVED: This is something we want to work on, exact details TBD<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 27 July 2021 16:57:29 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:27:25 UTC