- From: vmpstr via GitHub <noreply@w3.org>
- Date: Tue, 22 Jul 2025 21:10:48 +0000
- To: public-css-archive@w3.org
> But it means that the animation behavior can't be controlled very explicitly, and you can't combine multiple triggers on a single animation (for example, having an animation start/stop based on a timeline, but pause/unpause based on a button click). Although this is interesting to support, I wonder if there are specific use-cases you had in mind. It seems a little strange to have a timeline trigger, which can specify two different ranges for its "start" and "end" events, to only have one of them potentially have an effect. Presumably if the timeline trigger is specified in the animation-start-trigger, it would react to the "start" event (from the entry range) and if it's specified in the animation-end-trigger, it would react to the "end" event (from the continuation range)? By comparison, event triggers would presumably only have one "event" which can act as both. I wonder maybe if the timeline-trigger would then only really need one range and depending on where it's specified, it would react to entering the range or exiting the range. On a separate note, I think the behavior of "once" and "always" are analogous to animation-iteration-count where you can specify anything from 0 to infinite. Maybe we can do the same here. -- GitHub Notification of comment by vmpstr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12336#issuecomment-3104843339 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 22 July 2025 21:10:49 UTC