- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 29 Oct 2025 16:16:48 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-animations-2] Review of animation-trigger/etc text`. <details><summary>The full IRC log of that discussion</summary> <fantasai> TabAtkins: Discussed animation-trigger proposals, including at summer F2F<br> <fantasai> TabAtkins: Discussed a bunch of API questions during breakout, but not everyone was there<br> <fantasai> TabAtkins: So I collected all the resolutions we made, edited them in so can reviewed, and wanted to review them here.<br> <fantasai> TabAtkins: If any feedback, give now, or later, but want to put it in front of the WG for review<br> <fantasai> TabAtkins: Animations triggers kick off a time-based animation based on some kind of non-time-based trigger<br> <fantasai> TabAtkins: E.g. a scroll position<br> <fantasai> TabAtkins: There was also an interest in event-based animation triggers<br> <fantasai> TabAtkins: So a lot of different things interacting in same syntax space<br> <fantasai> TabAtkins: Current design splits into 2 bits<br> <fantasai> TabAtkins: First, triggers themselves get defined on an element.<br> <fantasai> TabAtkins: 2 types of triggers: timeline triggers, and event triggers<br> <fantasai> TabAtkins: These set up all the appropriate metadata for the trigger, most importantly its name as well as other options<br> <fantasai> TabAtkins: e.g. for timeline triggers it looks at the range, etc.<br> <fantasai> TabAtkins: We settled on a concept of a trigger can be stateful. Once it is entered, it won't fire another "enter" until it is "exited".<br> <fantasai> TabAtkins: For timeline triggers this is natural.<br> <fantasai> TabAtkins: For events this is optional, can also use statelessly<br> <fantasai> TabAtkins: Once a trigger is defined, it is globally visible, like anchor-name<br> <fantasai> TabAtkins: We also resolved to change the scoping mechanism for animation-timeline to match, so that all three features follow the same naming/scoping rules<br> <fantasai> TabAtkins: You then use trigger elsewhere. Currently only for animations.<br> <fantasai> TabAtkins: animation-trigger property (new sub-property of animation) associates triggers with an animation.<br> <fantasai> TabAtkins: Provide a trigger name and then actions that the trigger should do when activated.<br> <fantasai> TabAtkins: E.g. enter a particular timeline range do X, exit timeline range do Y<br> <fantasai> TabAtkins: That's the overview.<br> <fantasai> TabAtkins: Lots of discussion about exactly what bits go on the trigger vs the animation. We think we have a good breakdown atm.<br> <fantasai> TabAtkins: Example, what if you have 2-d scroll triger (intersection of x and y scroll positions), that's possible to fit in. Doesn't change interaction with animation-trigger.<br> <fantasai> TabAtkins: The design should be easy to copy from animation-trigger to other things that needs triggered, just need to define appropriate actions there<br> <fantasai> TabAtkins: Open for comments, open issues, gonna send over to TAG review shortly<br> <ydaniv> q+<br> <fantasai> astearns: Ok, we'll leave issue open until sufficient review<br> <astearns> ack fantasai<br> <TabAtkins> fantasai: 1) It would help to see an example.<br> <TabAtkins> fantasai: 2) before requesting wider review, would be good to get WD so the review is requested on an official draft<br> <TabAtkins> astearns: that implies you're okay with saying it's okay to publish?<br> <TabAtkins> fantasai: if we want to take more time to review that's fine, but I don't think we should kick to the TAG until it's ready to publish<br> <astearns> ack ydaniv<br> <fantasai> ydaniv: Good summary. Only thing we deferred for now was some ideas about makign the API a bit nicer or simpler.<br> <fantasai> ydaniv: But we deferred those because some issues with trying to simplify.<br> <fantasai> ydaniv: What we have now works, is coherent, can improve later<br> <fantasai> astearns: Any specific issues open on those ideas?<br> <fantasai> ydaniv: Some ideas we discussed in previous issues, and we simply had to decide some different path, which is what we currently have.<br> <fantasai> ydaniv: I still need to read what Tab did<br> <fantasai> ydaniv: Also missing Web Animations API for it, but we can do at second stage.<br> <fantasai> TabAtkins: Yeah, I didn't do any OM work yet because that's frustrating to write and want to do it just once. ^_^<br> <fantasai> fantasai: I think we should give the WG an example before we sign off on this.<br> <TabAtkins> https://davmila.github.io/sta-demos/explore/<br> <TabAtkins> ScribeNick: TabAtkins<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13010#issuecomment-3462530259 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 29 October 2025 16:16:49 UTC