Skip to content

Commit 785bdb5

Browse files
committed
[css-anchor-position] Document why the allowed properties were chosen for that list. Remove corresponding issue.
1 parent 6e7ae33 commit 785bdb5

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
@@ -1448,13 +1448,16 @@ use of the ''revert'' or ''revert-layer'' values
14481448
acts as if the property was part of the [=Author Origin=].
14491449
(Thus, it instead reverts back to the [=User Origin=].)
14501450

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

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

0 commit comments

Comments
 (0)