- From: Bramus via GitHub <noreply@w3.org>
- Date: Tue, 07 Oct 2025 11:46:30 +0000
- To: public-css-archive@w3.org
Reading the last two comments, I believe it would require the syntax to be split into two parts, because I see that behaviors like `play-pause` are more like compound behaviors that set both the enter and exit in one go. So you’d either set `animation-trigger` to a `<dashed-ident>` followed by: - A single or two `<simple-behavior>`s - A signle `<compound-behavior>` - `<simple-behavior> = play | play-once | play-forwards | play-backwards | pause | reset | replay | none` - `<compound-behavior> = play-pause | play-alternate | play-reset` (Excluded from `<simple-behavior>` is `auto` because IUC that only makes sense for the exit behavior. So, all together, the full syntax would become: ``` <simple-behavior> = play | play-once | play-forwards | play-backwards | pause | reset | replay | none; <compound-behavior> = play-pause | play-alternate | play-reset; <enter-behavior> = <simple-behavior>; <exit-behavior> = <simple-behavior> | auto; <trigger-behavior> = [<enter-behavior> <exit-behavior>?] | <compound-behavior>; animation-trigger: [<dashed-ident> <trigger-behavior>]# ``` -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12611#issuecomment-3376525779 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 October 2025 11:46:30 UTC