Skip to content

Commit dd7edaa

Browse files
committed
[css-anchor-1] Stop implying that an element can have multiple implicit anchor elements.
1 parent bc27c11 commit dd7edaa

File tree

1 file changed

+9
-5
lines changed

1 file changed

+9
-5
lines changed

css-anchor-1/Overview.bs

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -316,8 +316,8 @@ might not be capable of anchoring the positioned element.
316316
which satisfies the following conditions:
317317

318318
* If |name| is not provided,
319-
but |query el| has one or more [=implicit anchor elements=],
320-
|el| is one of those elements.
319+
but |query el| has an [=implicit anchor element=],
320+
|el| is that element.
321321
* If |name| is provided,
322322
|el| is an [=anchor element=] with an [=anchor name=] of |name|.
323323
* Either |el| is a descendant of |query el|'s [=containing block=],
@@ -343,14 +343,18 @@ might not be capable of anchoring the positioned element.
343343
in anchor positioning.
344344
</div>
345345

346-
An element can have one or more <dfn export>implicit anchor elements</dfn>,
347-
defined by other features.
348-
This specification does not define any [=implicit anchor elements=] itself.
346+
An element can also have an <dfn export>implicit anchor element</dfn>,
347+
used when an [=anchor function=] doesn't specify an explicit [=anchor name=].
349348

350349
Note: The Popup API, for example,
351350
defines an [=implicit anchor element=] for a popup--
352351
the element that the popup is attached to.
353352

353+
Note: An element can have only one implicit anchor element.
354+
If we end up with multiple features defining
355+
potentially different [=implicit anchor elements=] on the same element,
356+
this specification will define a resolution order.
357+
354358
<!--
355359
███████ ██ ██ ████████ ████████ ████ ████████ ██████
356360
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██

0 commit comments

Comments
 (0)