- From: Emilio Cobos Álvarez via GitHub <noreply@w3.org>
- Date: Wed, 01 Oct 2025 13:54:59 +0000
- To: public-css-archive@w3.org
> If it was fine to observe stale style then we wouldn't really need interleaving at all.
I'm confused, it's totally fine to observe some kinds of stale styles. In the case of anchor positioning it's very obvious, doesn't the fallback and such happen once per frame already?
https://drafts.csswg.org/css-anchor-position-1/#fallback-apply ("At the time that [ResizeObserver](https://drafts.csswg.org/resize-observer-1/#resizeobserver) events are determined and delivered" ...)
In my mind the interleaving is needed to deal with nested things like container queries in one go. I don't think anchor positioning has the same requirement (the only requirement is layout order between anchor and the anchored thing).
The interleaving in anchor positioning IMO was a mistake, IMO. If I recall correctly, it was just done for animation purposes (so that functions resolve to pixels at computed-value time) and it doesn't work great for animations even. Otherwise you can just do anchor positioning at layout time just fine.
--
GitHub Notification of comment by emilio
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12732#issuecomment-3356472832 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 October 2025 13:55:00 UTC