From e259fdf399caa11158bac8ca9d230883d07f4c84 Mon Sep 17 00:00:00 2001 From: "Tab Atkins Jr." Date: Tue, 28 Apr 2026 11:19:41 -0700 Subject: [PATCH] =?UTF-8?q?Revert=20"[css-anchor-position-1]=20Specify=20s?= =?UTF-8?q?croll=20offset=20snapshot=20timing=20#10796=20=E2=80=A6"?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This reverts commit 54fd028ea990dfb4b8430e1f900c0678306d4cac. --- css-anchor-position-1/Overview.bs | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/css-anchor-position-1/Overview.bs b/css-anchor-position-1/Overview.bs index eb2d10336d76..cee9b4434598 100644 --- a/css-anchor-position-1/Overview.bs +++ b/css-anchor-position-1/Overview.bs @@ -1075,9 +1075,6 @@ while still allowing as much freedom to anchor to various elements as possible, [=anchor positioning=] uses a combination of [=remembered scroll offsets=] and [=compensating for scroll=]. -The scroll offsets which are used to compute [=remembered scroll offsets=] and [=default scroll shift=] -are snapshotted when asked to [=run snapshot post-layout state steps=]. -
The details here are technical, but the gist is: @@ -1239,6 +1236,10 @@ specifically, the [=default anchor element=]: as if affected by a [=transform=] (before any other transforms). + Issue: Define the precise timing of the snapshot: + updated each frame, + before style recalc. + Issue: Similar to [=remembered scroll offset=], can we pay attention to transforms on the [=default anchor element=]?