- From: David A via GitHub <noreply@w3.org>
- Date: Tue, 09 Sep 2025 20:24:54 +0000
- To: public-css-archive@w3.org
To briefly capture the proposal on which we'd like a resolution:
We previously [resolved on](https://github.com/w3c/csswg-drafts/issues/12611#issuecomment-3206863438) the format for `animation-trigger` as:
```
/*trigger name*/ /*action*/ /*behavior*/
animation-trigger: [ [ trigger(<dashed ident>, <ident> <ident>)]+ ]#
```
which:
- required explicitly specifying an ident for the action and an ident for the behavior, and
- made use of "higher-level" actions which were declared on the `event-trigger`.
Our **proposed amendment** is the following:
```
(optional)
/*trigger name*/ /*action*/ /*behavior*/
animation-trigger: [ [ trigger(<dashed ident>, [<ident>] <ident>) ]+ ]#
```
which:
- does not make use of higher-level actions,
- makes specifying an ident for the action optional:
- if no action is provided, the behavior is associated with all actions declared on the `event-trigger` or, in the case of a `timeline-trigger`, the "enter" action.
- e.g. `trigger(--foo, play)` is equivalent to `trigger(--foo, enter play)`
- `timeline-trigger`'s "exit" action is the special case - to bind to an "exit" action, `animation-trigger` must specify "exit \<behavior\>."
- e.g. to play on exit, you have to specify `trigger(--foo, exit play)`
--
GitHub Notification of comment by DavMila
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12652#issuecomment-3272156757 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 9 September 2025 20:24:54 UTC