- From: Ian Kilpatrick via GitHub <noreply@w3.org>
- Date: Mon, 03 Aug 2026 19:06:53 +0000
- To: public-css-archive@w3.org
The most important thing we want to preserve (which everyone is doing today) is not triggering a relayout when we scroll (and some edge of the anchored element **doesn't** hit the edge of the scrollport). (aka. We don't want to trigger a relayout on every scroll just because you used anchor positioning). From here: Firefox/Chrome Mobile trigger a relayout (and give the popup additional size) when the ICB changes size due to hidey bars appearing disappearing. I'm not sure we can mitigate this as ICB changes can happen for multiple reasons (e.g. window resizing, orientation change, etc) and even on "mobile". Safari Desktop just seems to be not remembering the scroll offsets on various types of style changes which seems incorrect. The difference between Firefox Desktop and Chrome Desktop is the remembered scroll offsets recalculation triggered by https://drafts.csswg.org/css-anchor-position-1/#anchor-recalculation-point . Firefox is inserting one when the insets change(?) it appears. I'd be happy if we add a recalculation point if some set of properties change on the anchored element (aligning with Firefox current behaviour). -- GitHub Notification of comment by bfgeek Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/14112#issuecomment-5170601742 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 3 August 2026 19:06:54 UTC