Re: [csswg-drafts] [web-animations-2][css-animations-2] Set of actions for animation triggers (#12611)

The CSS Working Group just discussed `[web-animations-2][css-animations-2] Set of actions for animation triggers`.

<details><summary>The full IRC log of that discussion</summary>
&lt;kbabbitt> DavidA: this issue is about specifying the set of keywords we use to describe what an animationtrigger will do to an animation when correct conditions are mety<br>
&lt;kbabbitt> ... initially had higher level behaviors mostly focused on scroll triggered cases<br>
&lt;kbabbitt> ... now that we have event triggers, more fine grained options make sense<br>
&lt;kbabbitt> ... work same way for both types of triggers, also in cases where 2 types of triggers are mixed<br>
&lt;kbabbitt> ... example, play an animation when a thing is scrolled into view, pause when clicked<br>
&lt;kbabbitt> ... play animation when clicked, reset when it's scrolled out<br>
&lt;kbabbitt> ... that's what that table in the issue gives us<br>
&lt;ydaniv> q+<br>
&lt;astearns> ack ydaniv<br>
&lt;PaulG> q+<br>
&lt;kbabbitt> ydaniv: I'm fine with the dable<br>
&lt;kbabbitt> ... just added a comment that the last one can be play reset if we want to be consistent with naming<br>
&lt;ydaniv> s/dable/table/<br>
&lt;kbabbitt> s/dable/table<br>
&lt;kbabbitt> DavidA: the last one differs from play pause in that it's replay option<br>
&lt;kbabbitt> ... I added that one because in some event cases you want the interaction of click to forcefully reset animation and start playhing again<br>
&lt;kbabbitt> ... whereas in general play case you don't want that<br>
&lt;kbabbitt> flackr: think suggestion was just about name<br>
&lt;kbabbitt> fantasai: I think that wouldn't work because play-pause alternates between playing and pausing depending on current state<br>
&lt;kbabbitt> ... whereas this one doesn't matter what you're doing<br>
&lt;kbabbitt> ... if you're playing it resets and continues playing<br>
&lt;kbabbitt> ... I think replay is the correct name here<br>
&lt;ydaniv> q+<br>
&lt;astearns> ack fantasai<br>
&lt;astearns> ack PaulG<br>
&lt;kbabbitt> fantasai: this table makes a lot of sense<br>
&lt;kbabbitt> PaulG: looking at this, trying to catch up<br>
&lt;kbabbitt> ... I see where there's event trigger actions you can click or press a key<br>
&lt;kbabbitt> ... keyboard accessible which is great<br>
&lt;kbabbitt> ... things like play-pause button would have an accessible name, not sure how we're treating this<br>
&lt;kbabbitt> ... how does the current state get conveyed<br>
&lt;kbabbitt> ... those are the questions I'd raise, along with passing API back for wider review<br>
&lt;kbabbitt> fantasai: the thing that triggers these is handled in another conversation<br>
&lt;kbabbitt> ... this is just, once an event causes an action, these are actions author would choose<br>
&lt;kbabbitt> PaulG: 12336?<br>
&lt;kbabbitt> fantasai: 12562<br>
&lt;kbabbitt> DavidA: other issues probably relevant are 12562 and 12336<br>
&lt;astearns> ack ydaniv<br>
&lt;kbabbitt> ydaniv: okay to add a replay action behavior<br>
&lt;kbabbitt> ... this is introducing something new but I think it's fine<br>
&lt;kbabbitt> ... still need something that does alternating between play and reset<br>
&lt;kbabbitt> ... still need play-reset<br>
&lt;kbabbitt> astearns: we are at time, suggest what to add could be a separate issue<br>
&lt;kbabbitt> ... flackr, you had said we could do without initial column?<br>
&lt;kbabbitt> flackr: yes, it's not adding any value<br>
&lt;kbabbitt> ... from web animation perspective, there's no difference, no initial state<br>
&lt;kbabbitt> ... my suggestion is just don't have that<br>
&lt;kbabbitt> astearns: we're at time but it sounds like everyone is good with this?<br>
&lt;kbabbitt> ydaniv: I'm good if we just add this extra one because it's already in spec and consistent with other actions<br>
&lt;kbabbitt> ... not something new, including something that was dropped<br>
&lt;kbabbitt> DavidA: I think it makes sense to add this one too but want to clarify, it wasn't actually dropped<br>
&lt;kbabbitt> ... behavior in spec that already existed was captured by play and reset words as a separate thing<br>
&lt;kbabbitt> ... together enable existing functionality<br>
&lt;kbabbitt> ... what I think is okay to add as a new thing, wouldn't be thing that currently exists<br>
&lt;kbabbitt> ydaniv: like when you have play-alternate, play-pause<br>
&lt;kbabbitt> ... together we have play-reset<br>
&lt;kbabbitt> astearns: we're out of time, suggest we take back to issue<br>
&lt;kbabbitt> ... ydaniv and DavidA, please talk about how current play-reset functionality is accommodated<br>
&lt;kbabbitt> ... hopefully we can resolve quickly next week<br>
</details>


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


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

Received on Wednesday, 1 October 2025 17:03:06 UTC