Re: [csswg-drafts] [css-animations-2] Should there be 2 trigger-scope properties? (#13279)

> I see no reason to have the scope be shared when `event-trigger` and `timeline-trigger` names are independent.

I wasn’t 100% following along during the early discussions, but I always took it for granted that the names were not independent – similar to `{scroll|view}-timeline` which @ydaniv already pointed out. This was also reconfirmed during the F2F in Paris in which we decided to add `trigger-scope` (https://github.com/w3c/csswg-drafts/issues/12581#issuecomment-3206707173)

Using the same namespace allows one to have different types of triggers for different types of devices (for example), although I can’t really come up with a scenario where you’d want to switch from an `event-trigger` to a `timeline-trigger`.

Passing over to @DavMila / @flackr / @szager-chromium to chime in here.

> Currently we resolved to change the behavior of this property to limit scope instead of "lifting" it

Yes, see https://github.com/w3c/csswg-drafts/pull/13241 for the PR. This is also how it’s implemented in Blink.

Note that we also resolved in https://github.com/w3c/csswg-drafts/issues/12581#issuecomment-3206707173 to do the same for `timeline-scope`, in order to have all `*-scope` properties work in a similar manner.

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


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

Received on Monday, 5 January 2026 10:01:55 UTC