Skip to content

Commit 54fd028

Browse files
lillestabatkins
andauthored
[css-anchor-position-1] Specify scroll offset snapshot timing #10796 (#13675)
* [css-anchor-position-1] Specify scroll offset snapshot timing #10796 Specify that scroll offsets are snapshotted when asked to run snapshot post-layout state steps. Also see HTML PR[1] for when "run snapshot post-layout state steps" are expected to be run. [1] whatwg/html#11613 * Apply suggestion from @tabatkins (just rewrapping to semantic line breaks) --------- Co-authored-by: Tab Atkins Jr. <jackalmage@gmail.com>
1 parent 16a9725 commit 54fd028

1 file changed

Lines changed: 3 additions & 4 deletions

File tree

css-anchor-position-1/Overview.bs

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1075,6 +1075,9 @@ while still allowing as much freedom to anchor to various elements as possible,
10751075
[=anchor positioning=] uses a combination of [=remembered scroll offsets=]
10761076
and [=compensating for scroll=].
10771077

1078+
The scroll offsets which are used to compute [=remembered scroll offsets=] and [=default scroll shift=]
1079+
are snapshotted when asked to [=run snapshot post-layout state steps=].
1080+
10781081
<div class=note>
10791082
The details here are technical, but the gist is:
10801083

@@ -1236,10 +1239,6 @@ specifically, the [=default anchor element=]:
12361239
as if affected by a [=transform=]
12371240
(before any other transforms).
12381241

1239-
Issue: Define the precise timing of the snapshot:
1240-
updated each frame,
1241-
before style recalc.
1242-
12431242
Issue: Similar to [=remembered scroll offset=],
12441243
can we pay attention to transforms on the [=default anchor element=]?
12451244

0 commit comments

Comments
 (0)