Skip to content

Commit c67826d

Browse files
committed
[css-anchor-1][editorial] Add note making it clearer that non-none fallback prevents anchor(auto) from creating fallback entries. #7757
1 parent 8cc0e7f commit c67826d

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

css-anchor-1/Overview.bs

+13
Original file line numberDiff line numberDiff line change
@@ -321,6 +321,18 @@ consisting of two entries:
321321
and the ''anchor()/auto''/''auto-same'' keywords
322322
resolved to the opposite sides as well.
323323

324+
Note: If the element has a non-none 'position-fallback',
325+
these extra entries aren't added.
326+
Since the [=position fallback list=] styles
327+
override the "base" styles immediately,
328+
this will <em>usually</em> mean you wouldn't see a "base" ''anchor(auto)''
329+
show up in the final styles at all,
330+
but if that does happen
331+
(it's specified in a property
332+
that isn't overriden by anything in the [=position fallback list=]),
333+
the only effect of the ''anchor()/auto''/''auto-same''
334+
is to resolve to the appropriate side keyword.
335+
324336
<div class=example>
325337
For example, the following code using [=automatic anchor positioning=]:
326338

@@ -364,6 +376,7 @@ as specified above,
364376
if they would validly trigger [=automatic anchor positioning=].
365377

366378

379+
367380
<!--
368381
███ ██████ ████ ████████ ████████ ███ ███
369382
██ ██ ██ ██ ██ ██ ██ ██ ██

0 commit comments

Comments
 (0)