- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Thu, 06 Nov 2025 01:08:04 +0000
- To: public-css-archive@w3.org
This lack of scroll adjustment is intentional, yes. We're only allowed to compensate for one scroller (because different scrollers can be on different hardware-acceleration threads). We explicitly decided *not* to base the "which scroller?" decision on closely inspecting the `anchor()` functions, because you can use multiple anchor()s referring to anchors in different scrollers (including complex cases like `anchor(--default top, anchor(--another top))` - is that two different references, or one? which one?), and that felt too fragile. So, yes, even though in this example the --another anchor happens to always track --default in terms of vertical scroll, it *is* still in a separate scroller, so the abspos ends up with no references to anchors in the same scroller as its default anchor, and thus no scroll adjustment occurs. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12842#issuecomment-3494350546 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 6 November 2025 01:08:05 UTC