- From: Robert Flack via GitHub <noreply@w3.org>
- Date: Wed, 15 Oct 2025 13:25:38 +0000
- To: public-css-archive@w3.org
We've had a few resolutions on the trigger syntax in #12652 and #12336 which it looks like have not been reflected into this PR yet. In particular, we switched to `event-trigger-*` properties for event triggers, and decided that all triggers can have an activated / deactivated state with a list of events to progress into and out of the activated state. If no exit events specified it doesn't stay in the activated state or trigger exit behaviors (behaving much like the current design). Behaviors are also for now not a part of the resolved behavior so we don't need event specific behaviors as we'll have a common set of actions #12611 which can be associated with activation (and optionally deactivation). -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/12314#issuecomment-3406444923 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 October 2025 13:25:38 UTC