Skip to content

Commit dd4a553

Browse files
committed
[css-anchor-1] Make it clearer that the automatic anchor positioning stuff only applies when the anchor(auto) is used validly.
1 parent 1c2132c commit dd4a553

1 file changed

Lines changed: 5 additions & 4 deletions

File tree

css-anchor-1/Overview.bs

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@ The ''anchor()'' function has three arguments:
133133

134134
The <dfn value for=anchor()>auto</dfn> keyword
135135
indicates [=automatic anchor positioning=].
136-
See [[#auto-anchor]] for details.
136+
See [[#anchor-auto]] for details.
137137

138138
The physical <<anchor-side>> keywords
139139
(<dfn value for=anchor()>left</dfn>,
@@ -284,14 +284,15 @@ causing the element to automatically stick "next to" the [=anchor element=]
284284
in the most obvious way,
285285
and flip to the other side if necessary.
286286

287-
[=Automatic anchor positioning=] is only valid
287+
[=Automatic anchor positioning=] is only active
288288
if the opposite [=inset property=] is ''top/auto''.
289289
(For example, if an element had ''top: anchor(auto);'',
290290
it would have to also have ''bottom: auto;''.)
291291
If this is not the case,
292-
the ''anchor()'' function represents an [=invalid anchor query=].
292+
the ''anchor()'' function represents an [=invalid anchor query=],
293+
and the element does not use [=automatic anchor positioning=] in that axis.
293294

294-
When used in a given [=inset property=],
295+
When using [=automatic anchor positioning=],
295296
the ''anchor()/auto'' <<anchor-side>>
296297
behaves as the opposite side of the property it's used in.
297298
That is, when used in ''top: anchor(auto);'',

0 commit comments

Comments
 (0)