Skip to content

Commit 5e43940

Browse files
committed
[css-anchor-1] Use term to solve CB ambiguity problem #12830
1 parent a4f08e4 commit 5e43940

File tree

1 file changed

+1
-12
lines changed

1 file changed

+1
-12
lines changed

css-anchor-position-1/Overview.bs

Lines changed: 1 addition & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -425,7 +425,7 @@ in anchor positioning.
425425

426426
* |possible anchor| is laid out strictly before |positioned el|,
427427
aka one of the following is true:
428-
* |possible anchor| and |positioned el| share a [=containing block=]
428+
* |possible anchor| and |positioned el| have the same [=original containing block=]
429429
and either
430430
* |possible anchor| is [=in a lower top layer=] than |positioned el|, or
431431
* they both exist in the same [=top layer=],
@@ -435,17 +435,6 @@ in anchor positioning.
435435
(if one exists)
436436
is an [=acceptable anchor element=] for |positioned el|
437437

438-
Issue: “Share a containing block” isn't strictly correct;
439-
for example, two [=absolutely positioned boxes=]
440-
contained by the same [=grid container=] but with different 'grid-area' values
441-
get different [=containing blocks=],
442-
but should treat them as equivalent for this case.
443-
On the other hand, a scroller's [=fixed containing block=]
444-
and that same scroller's [=local containing block=]
445-
are using different [=containing blocks=] for this purpose
446-
(for example the [=initial fixed containing block=] contains the [=initial containing block=]).
447-
Need a better notion of “equivalent” [=containing blocks=] here.
448-
449438
* If |possible anchor| is in the [=skipped contents=] of another element,
450439
then |positioned el| is in the [=skipped contents=] of that same element.
451440

0 commit comments

Comments
 (0)