- From: Yehonatan Daniv via GitHub <noreply@w3.org>
- Date: Tue, 07 Oct 2025 13:21:44 +0000
- To: public-css-archive@w3.org
I think the idea was not to distinguish the compound behaviors syntactically, but rather to add the `auto` value as the initial value for the exit behavior to bridge that gap.
So the following works:
```css
.target {
event-trigger: --trigger pointerenter / pointerleave;
animation-trigger: --trigger play-alternate /* (auto) */;
}
```
And also this should work:
```css
.target {
event-trigger: --trigger click;
animation-trigger: --trigger play-alternate;
}
```
And even this:
```css
.target {
event-trigger: --trigger click / click;
animation-trigger: --trigger play-alternate /* (auto) */;
}
```
----------
Now, with the granular behaviors we get:
```css
.target {
event-trigger: --trigger pointerenter / pointerleave;
animation-trigger: --trigger play /* (auto) */;
}
```
And the `pointerleave` is mapped to `none`, so this will play once on `pointerenter` and that's it.
OTOH, if you specify this:
```css
.target {
event-trigger: --trigger click;
animation-trigger: --trigger play-forwards play-backwards;
}
```
Then the `play-forwards` is never triggered since there's no event mapped to it.
--
GitHub Notification of comment by ydaniv
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12611#issuecomment-3376874255 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 13:21:45 UTC