- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 23 Jul 2025 16:25:45 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[web-animations-2][css-animations-2] Should an animation be allowed to have multiple triggers associated?`, and agreed to the following: * `RESOLVED: we allow one trigger per animation for now, throw in JS if someone tries to add more than one, and have an explicit intent to allow multiple in the future` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> David: we're trying to figure out if there should be a way to specify multiple triggers that can play a single animation<br> <TabAtkins> David: there's some concern about, if an animation has multiple triggers, there should be some default coordination between the triggers<br> <TabAtkins> David: here's an example - a timeline trigger in one axis, and a timeline trigger in another axis, maybe the author's intention is really about the intersection of those two axises?<br> <TabAtkins> David: proposal in the issue right now is to allow only one trigger per animation, provided we can allow for multiple triggers in the future<br> <masonf> Lea: best discussion of the "action" for interest invokers happened here. https://github.com/openui/open-ui/issues/1064<br> <TabAtkins> David: the JS API, if you try to attach multiple triggers to an animation, an error would throw<br> <TabAtkins> David: an issue probably needs to be filed for how to deal with multiple triggers of the same name<br> <TabAtkins> q+<br> <ydaniv> ScribeNick: ydaniv<br> <astearns> ack TabAtkins<br> <ydaniv> TabAtkins: fantasai and I did some design work and added suggestions<br> <fantasai> -> https://github.com/w3c/csswg-drafts/issues/12336#issuecomment-3091201201<br> <ydaniv> ... we think allowing multiple triggers makes sense<br> <ydaniv> ... while exploring this we think it's complicated<br> <ydaniv> ... there's a potential for batching triggers, you might want to intersect triggers<br> <ydaniv> ... there's more to explore here<br> <ydaniv> ... I'm ok to adopting resolution to defer for now<br> <ydaniv> ... any grammar here that allows 1 trigger will be extensible later so we should be safe<br> <ydaniv> flackr: for this future discussion, does it make sense to add comma separated, and with in space separated triggers?<br> <ydaniv> TabAtkins: perfectly fine<br> <fantasai> s/add comma/have comma/<br> <ydaniv> flackr: I think it would be good to add space separated<br> <fantasai> s/with in/within add/<br> <ydaniv> ... agree<br> <TabAtkins> ScribeNick: TabAtkins<br> <ydaniv> q+<br> <TabAtkins> David: to be clear, when we say single trigger per animation, we do still mean that the animation has a start and end trigger, those are just one trigger<br> <astearns> ack ydaniv<br> <TabAtkins> ydaniv: agree with the discussion so far<br> <TabAtkins> astearns: so if i'm following, current resolution is only one trigger per animation for now, and have a note about how we might do multiple in the future<br> <TabAtkins> flackr: yes, and we want to throw an error in JS to make it clear that it's an extension point<br> <TabAtkins> flackr: the syntax in the spec doesn't currently allow multiple in CSS, we'll just make that official for now<br> <TabAtkins> astearns: so proposed is we allow one trigger per animation for now, throw in JS if someone tries to add more than one, and have an explicit intent to allow multiple in the future<br> <TabAtkins> astearns: objections?<br> <TabAtkins> RESOLVED: we allow one trigger per animation for now, throw in JS if someone tries to add more than one, and have an explicit intent to allow multiple in the future<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12399#issuecomment-3109330018 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 July 2025 16:25:46 UTC