Re: [csswg-drafts] [css-animations-2] Proposal: Time-based Keyframe Animations (#4907)

The CSS Working Group just discussed `[css-animations-2] Proposal: Time-based Keyframe Animations`, and agreed to the following:

* `RESOLVED: Draft up proposal for time-based keyframe selectors in Anim 2`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> astearns: Anyone want to propose something for this, or just continue discussing in an issue?<br>
&lt;TabAtkins> fantasai: If we want to do, we can draft. If we'r enot sure, we can figure out the scope<br>
&lt;TabAtkins> miriam: I've heard lots of requests for this<br>
&lt;fantasai> TabAtkins: prsumably would work as we just discussed<br>
&lt;emeyer> TabAtkins: I presume it work in a way similar to what we just discussed<br>
&lt;TabAtkins> fantasai: Right, I think we have to think about these two together.<br>
&lt;TabAtkins> fantasai: So if we want to do this we can resolve it and figure out the issues together<br>
&lt;TabAtkins> miriam: is 100% the final time?<br>
&lt;TabAtkins> fantasai: That question is also relevant for the previous issue.<br>
&lt;TabAtkins> TabAtkins: Like is it duration, or duration+delay?<br>
&lt;emeyer> TabAtkins: Is it the duration, or is it the duration plus the dleay?  Is that the question?<br>
&lt;flackr> q+<br>
&lt;TabAtkins> miriam: Or final keyframe<br>
&lt;astearns> ack astearns<br>
&lt;astearns> ack fantasai<br>
&lt;astearns> ack flackr<br>
&lt;TabAtkins> flackr: I think this is similar to range-based keyframes<br>
&lt;TabAtkins> flackr: Where they're converted to %s of the animation<br>
&lt;TabAtkins> flackr: The precedent we set is they don't set the range of the animation itself, they can go before beginning and after end<br>
&lt;TabAtkins> flackr: I can see if you use duration:auto if picks up the greatest duration specified in keyframes<br>
&lt;emeyer> TabAtkins: That would make sense if we ever do things like spring-timing functions<br>
&lt;TabAtkins> flackr: Yeah<br>
&lt;TabAtkins> flackr: But otherwise the default model should be the span is the animation duration, time values before/after that are clipped<br>
&lt;TabAtkins> +1<br>
&lt;TabAtkins> fantasai: That's different from... well what happens when you iterate?<br>
&lt;TabAtkins> fantasai: [missed]<br>
&lt;TabAtkins> flackr: Think it's consistent with range-based keyframes<br>
&lt;TabAtkins> flackr: They convert as if you have one iteration, and you shorten<br>
&lt;TabAtkins> fantasai: We'd do that here?<br>
&lt;TabAtkins> flackr: Yeah, don't think you want subsequent iterations to be different form earlier ones<br>
&lt;TabAtkins> fantasai: Feel like something's not clicking but not sure.<br>
&lt;TabAtkins> fantasai: But if we want to see this we should resolve on it and draft it, and see how all these keyframe types work together to make sure they're consistent<br>
&lt;TabAtkins> astearns: Anyone think we shouldn't work on it?<br>
&lt;TabAtkins> astearns: So options are (1) continue to work on details in the issue, or (2) put a draft in Animations 2<br>
&lt;TabAtkins> astearns: Anyone prefer leaving it in issue?<br>
&lt;TabAtkins> astearns: Anyone object to starting work on this in Anim 2?<br>
&lt;TabAtkins> RESOLVED: Draft up proposal for time-based keyframe selectors in Anim 2<br>
</details>


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


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

Received on Wednesday, 12 April 2023 16:26:27 UTC