- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 24 Sep 2025 16:49:48 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[web-animations-2][css-animations-2] animation-trigger CSS syntax`, and agreed to the following: * `RESOLVED: syntax of animation-trigger is [<dashed-ident> <behavior/actions>]+#` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> fantasai: two things. first here is the syntax of animation-trigger, which binds a named event to an animation<br> <TabAtkins> fantasai: given that comma-separated is already used to align them with the animations<br> <TabAtkins> fantasai: we need something else. could use a trigger() function, but maybe awkward<br> <TabAtkins> fantasai: I think the current syntax proposed is to use space separation, with name first then actions<br> <TabAtkins> fantasai: and because the event is syntax unique, it would go first and dictate what arguments would apply to it<br> <flackr> something like [<dashed-ident> <behavior/actions>]+ ?<br> <TabAtkins> fantasai: yes, like that<br> <futhark> present-<br> <TabAtkins> flackr: seems reasonable<br> <TabAtkins> ydaniv: sounds fine. Robert had some concerns about later having multiple triggers....<br> <TabAtkins> flackr: that's implied here<br> <TabAtkins> flackr: the dashed-ident doesnt' clash with the behavior/action values<br> <TabAtkins> fantasai: an alternative is to flip the order.... but that could be confusing<br> <TabAtkins> proposed resolution: syntax of animation-trigger is [<dashed-ident> <behavior/actions>]+#<br> <TabAtkins> RESOLVED: syntax of animation-trigger is [<dashed-ident> <behavior/actions>]+#<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12652#issuecomment-3329841437 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 September 2025 16:49:49 UTC