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

Trying to catch up with this issue, apologies if I'm re-hashing things that have already been discussed. I'm not sure whether that holds, but my understanding was that a design goal of this feature was to allow user-agents to implement animation triggers in a way where they could trigger an animation more responsively than a page could by adding event listeners and triggering animations using existing functionality. For instance, a click on an element could trigger an animation immediately without going through event dispatch.

Assuming that is true, I was wondering what the expected behavior for calling `preventDefault()` would be and if there were general provisions for overriding via script what was specified via CSS.

The reason I'm asking this is that from an implementor's perspective, I expect the idea would be that we could have all the information for animations to be started via an animation trigger stored in a separate thread / process and act on them without involving the web process / main thread. But I don't understand how this is feasible given the complexity of event dispatch.

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


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

Received on Thursday, 18 September 2025 07:46:28 UTC