- From: David A via GitHub <noreply@w3.org>
- Date: Wed, 20 Aug 2025 17:18:42 +0000
- To: public-css-archive@w3.org
> Later discussion with [@fantasai](https://github.com/fantasai) led to some more possibility: rather than _only_ having event sources emit naked events caught by trigger(), have them (a) also emit "higher-level" events (like `activate`), and (b) let authors bind one or more events to a chosen name, so you can semantically group some events together. > > So: > > ``` > .source { > event-trigger-name: --foo; > event-trigger-actions: --bar click press("k"), --baz press("Enter"); > /* the --foo event trigger source defined two named actions, --bar and --baz. */ > } > .anim { > animation: my-anim; > animation-trigger: trigger(--foo, --bar play, --baz pause, press("Escape") reset); > /* can refer to multiple trigger actions, either by "action name" or directly */ > } > ``` And I guess for a timeline trigger we'd have: ```css .source { timeline-trigger-name: --view-trigger; timeline-trigger-source: view(); timeline-trigger-entry-range-block: contain; timeline-trigger-actions: --enter enter; } .target { animation-trigger: trigger(--view-trigger, --enter play-forwards, exit play-backwards); } ``` -- GitHub Notification of comment by DavMila Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12611#issuecomment-3207358173 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 20 August 2025 17:18:43 UTC