- From: Yehonatan Daniv via GitHub <noreply@w3.org>
- Date: Wed, 24 Sep 2025 13:42:41 +0000
- To: public-css-archive@w3.org
> Choose between having higher-level ["behaviors"](https://drafts.csswg.org/css-animations-2/#propdef-animation-trigger-behavior) and granular "actions" such as those proposed in https://github.com/w3c/csswg-drafts/issues/12611#issuecomment-3292998336. I think there's an inflation of the use of the term `action` here. Basically these are all `behaviors`. AFAIU we used `action` to reference the type of event that tripped the trigger, [see here](https://github.com/w3c/csswg-drafts/issues/12611). But more importantly, I think we can settle on using something like the table in #12611, as long as all the behaviors that are currently in the spec are in there, grosso modo bikeshedding. > I am proposing the latter (granular actions) in order to support the mixing and matching of event-trigger and timeline-trigger as mentioned in Tab & Elika's https://github.com/w3c/csswg-drafts/issues/12336#issuecomment-3091201201 AFAIK, we still don't have a solution for mixing timeline triggers with other triggers, e.g. what happens when you enter a range and trigger `play`, then click to `pause`, and then scroll again. Will that trigger another `play`? That means the trigger needs to contain its current state, which we said we're avoiding for now. > We could eventually have high-level actions which are spec’d to map to granular actions. E.g. `alternate`... IIUC by "high-level" actions we meant defining events like `activate`, instead of click/keypress/etc. `alternate` is a behavior which I recall we already agreed should be included with the broken down behaviors. ----------------- > I don't especially love using trigger() as a mere grouping agent because we ran out of commas, so I somewhat lean towards @flackr's alternative suggestion of just using spaces. @flackr said we may need to keep the functional notation [here](https://github.com/w3c/csswg-drafts/issues/12652#issuecomment-3276502512), though I agree we this concern, so we need to clear this one out. -- GitHub Notification of comment by ydaniv Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12652#issuecomment-3328527489 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 September 2025 13:42:42 UTC