- From: Yehonatan Daniv via GitHub <noreply@w3.org>
- Date: Wed, 18 Jun 2025 17:15:08 +0000
- To: public-css-archive@w3.org
@DavMila @flackr I think I did get this got this confused, sorry. I'm ok with multiple animations per trigger, but not with multiple triggers per animation. I think we should keep `Animation.trigger` as a single object, and not change to `Animation.triggers` as a list. So I guess no objection to `AnimationTrigger.add(animation)` and `AnimationTrigger.remove(animation)` in general, except for: 1. Having the other direction: `Animation.triggers.add(trigger)`. That I believe would lead to something less useful. 2. Also ensuring that calling `AnimationTrigger.add(animation)` sets the `.trigger` property of that animation to that trigger, and not just adds it. If we agree on not allowing multiple triggers per animation that this should follow naturally from that resolution. -- GitHub Notification of comment by ydaniv Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12119#issuecomment-2985106010 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 June 2025 17:15:09 UTC