Re: [csswg-drafts] [css-animations-2] Move scroll and event animation triggers to independent namespace (#12336)

> One of the things that a separate …-trigger enables is the ability to have one element be the trigger, and then use that trigger as the animation-trigger on a different element. Similar to how a (named) view-timeline can be used as the animation-timeline on a totally different element.

Of course, maybe I wasn't clear in my comment above:

> Then we need to decide on something like adding a trigger-event property which allows setting a list of events

We need a new property to allow setting an ident and an event type on an element to declare an event. My placeholder name suggestion `trigger-event`, that accepts a list of event declarations.
This property will allow declaring an event source.

Then we can add the ability for `animation-trigger` to accept a reference to an event, could be with another sub-property like `animation-trigger-event`, only we need to differentiate that from `animation-trigger-timeline`, so conceptually suggesting a syntax like:

`<single-animation-trigger> = <single-animation-trigger-behavior> || [ none | auto | event(<dashed-ident>) | [ [ <dashed-ident> | <scroll()> | <view()> ] [ normal | <length-percentage> | <timeline-range-name> <length-percentage>? ]{0,4} ] ]`

Specifically see the __`event(<dashed-ident>)`__ addition.

What I objected to is removing the entire `animation-trigger` declaration into a separate no property, since I think that will only complicate the API and won't add any additional ability we don't currently have.

-- 
GitHub Notification of comment by ydaniv
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12336#issuecomment-2981561513 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 17 June 2025 19:14:17 UTC