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

> @SebastianZ: In general, I would prefer to reduce/minimize the number of moving parts, and your proposal goes in the opposite direction. I think it's possible to get the expressiveness this feature needs without using CSS functional syntax in an unorthodox way, and without separating out event descriptions into a separate longhand property.

Sorry for not responding earlier!

It depends on what you define as "moving parts". My proposal actually tries to _reduce_ the number of moving parts regarding the properties, as it only requires two new ones (or three if the shorthand is included) instead of six+. The controlling knobs would then be in the functions, instead. And I'd argue that their usage is _not_ unorthodox but rather reflecting what you're able to set for scroll animations.

The main benefit of this approach is that all trigger handling is centralized and unified and not directly related to animations.

Though I still didn't find the time to give this a deeper thought, nor the other proposed solutions. So I don't have a strong opinion on this.

Sebastian

-- 
GitHub Notification of comment by SebastianZ
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12336#issuecomment-3206260747 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 13:05:58 UTC