[csswg-drafts] [scroll-animations-1] it is not clear when to update stale timelines (#12120)

graouts has just created a new issue for https://github.com/w3c/csswg-drafts:

== [scroll-animations-1] it is not clear when to update stale timelines ==
The [HTML Processing Model: Event loop section of the Scroll-driven Animations spec](https://drafts.csswg.org/scroll-animations-1/#event-loop) discusses how scroll and view timelines may become stale in the process of updating the rendering since timeline sources or subjects may change bounds during that process.

However, the spec does not reference the HTML spec with hard links and rather references sections which are by now outdated. For instance (at the time of writing this issue), the step to update animations and send events is step 11 and the current spec references step 10. As such it is not clear exactly when in the process of updating the page rendering stale timelines should be updated. Using informative notes, it appears it is after resize observers have been evaluated and styles have been recalculated and layout updated.

We should probably update the HTML spec itself to add a step that clearly references the process of updating stale timelines.

Here are related spec issues and spec change:

- [[scroll-animations] Behavior of scroll-linked animations in the first frame](https://github.com/w3c/csswg-drafts/issues/5261)
- [[scroll-animations-1] Handling changed size/position in current frame](https://github.com/w3c/csswg-drafts/issues/8694)
- [additional spec change](https://github.com/w3c/csswg-drafts/pull/8704)

Cc @flackr who made the spec change as well as @kevers-google and @andruud who reviewed it.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12120 using your GitHub account


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

Received on Friday, 25 April 2025 14:34:25 UTC