- From: Nick Coury via GitHub <noreply@w3.org>
- Date: Mon, 23 Feb 2026 19:14:02 +0000
- To: public-css-archive@w3.org
We've also run into this. You can see an example here on a cross-doc VT (slowed down for emphasis) - https://photos.app.goo.gl/CdcQVUyyYKcuoiheA I understand the reasons for anchoring to the viewport, but anchoring to scrolling seems like it would be the right default behavior more often than not given the new pseudos are live and will shift the majority of the viewport content. The only content in the old pseudo snapshots that wouldn't expect to move are sticky elements, and that makes up the minority of the visible content. The prevalence of this should be reduced once Scoped View Transitions are available, though in theory the same issue could arise in scrollers within the scoped content. It feels like a net improvement in smoothness and net reduction in jank change the default behavior to track scrolling, especially if it can be done on the compositor to avoid frame lags. Given the existing behavior is already very broken looking, I wouldn't be overly concerned about changing the behavior. If absolutely required, it could be an opt-in to decide whether to track scrolling and perhaps how to do the scroll tracking if multiple approaches are needed (root vs nested scroller). -- GitHub Notification of comment by nickcoury Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10197#issuecomment-3946781258 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 23 February 2026 19:14:03 UTC