Re: [csswg-drafts] [web-animations-2][css-animations-2] Should an animation be allowed to have multiple triggers associated? (#12399)

> Summary: I don't see the benefit in not allowing multiple triggers per animation at the moment. If authors want coordinated trigger behavior, it should not be implicit - they should specify it. I don't see a nice way of specifying it with the current set of properties we have so I think such specification will have to be an additive feature.
> 

Thinking about this a bit more, I'm getting a better sense of @ydaniv 's concerns about allowing multiple triggers per animation. We will probably want to specify the [`animation-trigger-behavior`](https://drafts.csswg.org/css-animations-2/#animation-trigger-behavior) in a way that makes sense for both event-based triggers and scroll-based triggers rather than having the behaviors have different meanings for the different types of triggers. Doing so in a way that makes sense where multiple triggers are allowed likely has complexity that we would want to take care to handle.

I support @ydaniv 's position of not allowing multiple triggers per animation to start. Script can enforce this by throwing an error when `AnimationTrigger.addAnimation` (or whatever we settle on in #12397) is called on a trigger which already has an animation attached.

-- 
GitHub Notification of comment by DavMila
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12399#issuecomment-3070671958 using your GitHub account


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

Received on Monday, 14 July 2025 19:11:55 UTC