@@ -1012,7 +1012,7 @@ Placement Precision: the 'masonry-slack' property</h3>
1012
1012
1013
1013
<pre class=propdef>
1014
1014
Name : masonry-slack
1015
- Value : <<length-percentage>>
1015
+ Value : <<length-percentage>> | infinite
1016
1016
Initial : 1em
1017
1017
Percentages : relative to the [=grid-axis=] [=content box=] size of the [=masonry container=]
1018
1018
Inherited : no
@@ -1035,7 +1035,7 @@ Placement Precision: the 'masonry-slack' property</h3>
1035
1035
causing them to fill in order.
1036
1036
1037
1037
<dl dfn-type=value dfn-for=masonry-slack>
1038
- : <dfn><<length>></dfn>
1038
+ : <dfn><<length-percentage >></dfn>
1039
1039
:: Specifies the <dfn dfn for=masonry>tie threshold</dfn>
1040
1040
for the [=masonry container=] .
1041
1041
Placement positions are considered to be equally good (“tied”)
@@ -1044,6 +1044,19 @@ Placement Precision: the 'masonry-slack' property</h3>
1044
1044
1045
1045
Note: The initial value is a “small” distance (''1em'' )
1046
1046
that is probably appropriate to represent “close enough”.
1047
+
1048
+ : <dfn>infinite</dfn>
1049
+ :: Specifies an infinite [=tie threshold=] .
1050
+ This makes items distribute themselves strictly in order,
1051
+ without considering the length of the tracks at all.
1052
+
1053
+ Note: This value can result in consecutive items being placed
1054
+ in dramatically different positions in the [=stacking axis=] ,
1055
+ which can be confusing to readers.
1056
+ If the initial value (`1em`) is too small,
1057
+ consider a larger value (such as `10em` or `50vh`)
1058
+ instead of `infinite`.
1059
+
1047
1060
</dl>
1048
1061
1049
1062
Issue: Is ''1em'' the right default?
0 commit comments