Skip to content

Commit f7b4eb4

Browse files
committed
[css-anchor-position] Add issue about position-fallback-bounds being a more generic ability
1 parent aab83ec commit f7b4eb4

File tree

1 file changed

+17
-0
lines changed

1 file changed

+17
-0
lines changed

css-anchor-position-1/Overview.bs

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1235,6 +1235,17 @@ this property determines which [=position option=] to use.
12351235
</dl>
12361236
-->
12371237

1238+
The 'position-try' Shorthand {#position-try-prop}
1239+
-------------------------------------------------
1240+
1241+
<pre class="propdef shorthand">
1242+
Name: position-try
1243+
Value: <<'position-try-order'>>? <<'position-try-options'>>
1244+
</pre>
1245+
1246+
This shorthand sets both 'position-try-options' and 'position-try-order'.
1247+
If <<'position-try-order'>> is omitted,
1248+
it's set to the property's initial value.
12381249

12391250

12401251
<!-- Big Text: @pos-try
@@ -1367,6 +1378,12 @@ Animation type: discrete
13671378
Issue: padding-box? Or content-box? Should it be controllable?
13681379
</dl>
13691380

1381+
Issue: Or should this just be a more generic CSS Position ability,
1382+
where any abspos can select a specific element as its containing block?
1383+
Presumably still using the 'anchor-name' to specify it,
1384+
and applying the same constraints as described here,
1385+
to ensure proper ordering of layout
1386+
13701387

13711388
Applying Position Fallback {#fallback-apply}
13721389
--------------------------

0 commit comments

Comments
 (0)