- From: dshin-moz via GitHub <noreply@w3.org>
- Date: Mon, 06 Oct 2025 21:49:36 +0000
- To: public-css-archive@w3.org
So.. Ok, that answers the question about remembered scroll offset - That is, inset values of anchor positioned elements may represent values that aren't reachable by the scroller that it scrolls with. FWIW, with the [test case](https://github.com/user-attachments/files/22670224/asc2.html), with the first rAF uncommented, both Blink & WebKit behave like relative positioned elements where the in-flow positioned portion that always contributes to the scrollable overflow regardless of how far the visual portion is offset. In the testcase, positioned element's overflow at initial scroll positions (== remembered scroll offset with that first rAF), behaves like the in-flow portion of a relative-positioned element. Well... Except on WebKit (STP 20623.1.9.1), upon resizing the window, things update to behave more like @fantasai describes ([Bug filed](https://bugs.webkit.org/show_bug.cgi?id=300266)). -- GitHub Notification of comment by dshin-moz Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12898#issuecomment-3374354875 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 6 October 2025 21:49:37 UTC