- From: David A via GitHub <noreply@w3.org>
- Date: Wed, 25 Jun 2025 13:51:33 +0000
- To: public-css-archive@w3.org
DavMila has just created a new issue for https://github.com/w3c/csswg-drafts: == [web-animations-2][css-animations-2] How do AnimationTriggers attach to animations? == In #12119 we resolved to treat AnimationTriggers as "external controllers" of animations rather than an underlying mechanism for how animations play. With this model, we need an explicit way to associate AnimationTriggers with Animations. In #12119 We proposed `AnimationTrigger.addAnimation(Animation)` and `AnimationTrigger.removeAnimation(animation)`. I'm filing this issue separately as the main item in #12119 has been resolved on and that issue already has a pretty long thread. Picking up from @flackr's [suggestion](https://github.com/w3c/csswg-drafts/issues/12119#issuecomment-2912647102), some possible options are: - `AnimationTrigger.addAnimation(Animation)`/`AnimationTrigger.removeAnimation(animation)` which follows the pattern of `EventTarget.addEventListener`, - `AnimationTrigger.animations.add`/`AnimationTrigger.animations.remove` which follows the pattern of `Element.classList.` My preference would be for `AnimationTrigger.addAnimation`/`AnimationTrigger.removeAnimation`. @flackr @ydaniv @bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12397 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 June 2025 13:51:34 UTC