- From: David A via GitHub <noreply@w3.org>
- Date: Wed, 24 Sep 2025 14:50:37 +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 [#12611 (comment)](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). > Yeah I guess I'm using the terms a bit loosely here. I call them "actions" here just to differentiate from `alternate`, `repeat` etc which I call "behaviors." > > 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. > Right, I meant to write "higher-level **behaviors**." I've edited that. :) -- GitHub Notification of comment by DavMila Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12652#issuecomment-3329046856 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 14:50:38 UTC