- From: Seokho Song via GitHub <noreply@w3.org>
- Date: Mon, 20 Apr 2026 11:30:31 +0000
- To: public-css-archive@w3.org
Additionally, @andruud mentioned that we should specify the event timing in [the CL](https://chromium-review.googlesource.com/c/chromium/src/+/7656126).
Since the following specs are managed by HTML's event [loop-processing-model](https://html.spec.whatwg.org/multipage/webappapis.html#event-loop-processing-model):
- **[resize-observer Algorithms](https://drafts.csswg.org/resize-observer/#algorithms):**
> Note: The following algorithms are invoked as a part of update the rendering in the html spec: gather active resize observations at depth, has active resize observations, has skipped resize observations, broadcast active resize observations and deliver resize loop error notification.
- **[css-conditional-5 Updating Scroll State](https://www.w3.org/TR/css-conditional-5/#updating-scroll-state):**
> To avoid such layout cycles, scroll-state query containers update their current state as part of run snapshot post-layout state steps which is only run at specific points in the HTML event loop processing model.
When asked to run snapshot post-layout state steps, update the current state of every scroll-state query container. This snapshotted state will be used for any style and layout updates until the next time these steps are run.
We should consider a similar approach here.
--
GitHub Notification of comment by DevSDK
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/13551#issuecomment-4280237523 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 20 April 2026 11:30:32 UTC