Re: [csswg-drafts] [css-transitions-1] Clarify timing of transitionrun and transitionstart (#11665)

> The transition may not yet have a start time if it is composited, which may be a good reason to defer transitionstart, however I think as a developer I would expect transitionrun to fire right away.

+1 to this suggestion. `transitionrun` not firing immediately _(in Chrome and Firefox at least)_ is currently an issue when building a [custom style observer](https://brm.us/style-observer) to respond to style changes: it fires a frame too late, potentially causing glitches [as explained here](https://www.bram.us/2024/11/25/experiment-automatically-triggered-view-transitions-with-mutationobserver/#shortcomings).

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


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

Received on Thursday, 6 February 2025 16:51:55 UTC