Skip to content

Commit 2ae4f8e

Browse files
committed
[css-anchor-position] Document why the allowed properties were chosen for that list. Remove corresponding issue. w3c#9946
2 parents 74c1986 + 785bdb5 commit 2ae4f8e

File tree

1 file changed

+10
-7
lines changed

1 file changed

+10
-7
lines changed

css-anchor-position-1/Overview.bs

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1565,13 +1565,16 @@ use of the ''revert'' or ''revert-layer'' values
15651565
acts as if the property was part of the [=Author Origin=].
15661566
(Thus, it instead reverts back to the [=User Origin=].)
15671567

1568-
1569-
Issue(#9195): What exactly are the constraints that determine what's allowed here?
1570-
Current list is based off of what's reasonable
1571-
from Chrome's experimental impl.
1572-
We can make a CQ that keys off of which fallback was used
1573-
to allow more general styling,
1574-
at least for descendants.
1568+
Note: The [=accepted @position-try properties=] are the smallest group of properties
1569+
that affect just the size and position of the box itself,
1570+
without changing its contents area.
1571+
This significantly simplifies the implementation of position fallback,
1572+
without reducing the possible behaviors overly much.
1573+
It is expected that a future extension to [=container queries=]
1574+
will allow querying an element
1575+
based on the position fallback it's using,
1576+
allowing many cases not allowed by this restricted list
1577+
to be handled.
15751578

15761579
Issue(#7758): Would be useful to be able to detect
15771580
when your anchor(s) are fully off-screen

0 commit comments

Comments
 (0)