- From: Yehonatan Daniv via GitHub <noreply@w3.org>
- Date: Tue, 07 Oct 2025 17:41:08 +0000
- To: public-css-archive@w3.org
Agree, we can resolve a basic, explicit model now, and try to enhance later. So if we follow that path, the "warts" we're left with are the following cases (please correct me if I'm wrong): Needing to explicitly state events and behaviors to get both activation and deactivation behaviors: ```css .target { event-trigger: --ev click / click; animation-trigger: --ev play-forwards play-backwards; } ``` And for timeline trigger we still have the longer syntax: ```css .target { timeline-trigger: --tl view(); animation-trigger: --tl play-farwards play-backwards; } ``` Otherwise, if the exit behavior is omitted it is `none`. -- GitHub Notification of comment by ydaniv Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12611#issuecomment-3377923202 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 17:41:09 UTC