Skip to content

Commit fc518f3

Browse files
committed
[css-break-3] Take suggestion to swap order of two points.
1 parent 9b28f33 commit fc518f3

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

css-break-3/Overview.bs

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -834,13 +834,8 @@ Breaking into Varying-size Fragmentainers</h3>
834834
When a flow is fragmented into varying-size fragmentainers, the following
835835
rules are observed for adapting layout:
836836
</p>
837-
<!-- try to make this clearer. Steve suggests swapping first two points, maybe break it up more? -->
837+
<!-- try to make this clearer. Steve suggested swapping first two points (done), maybe break it up more? -->
838838
<ul>
839-
<li>
840-
Intrinsic sizes are calculated and maintained across the entire element.
841-
Where an initial containing block size is needed to resolve an intrinsic
842-
size, assume the size of the first fragmentainer defining a fragmentation context.
843-
</li>
844839
<li>
845840
Layout is performed per-fragmentainer, with each fragmentainer continuing
846841
progress from the breakpoint on the previous, but recalculating sizes
@@ -852,6 +847,11 @@ Breaking into Varying-size Fragmentainers</h3>
852847
the UA may instead maintain a consistent <a>inline size</a> and resolved <a>block size</a>
853848
across fragmentainers.
854849
</li>
850+
<li>
851+
Intrinsic sizes are calculated and maintained across the entire element.
852+
Where an initial containing block size is needed to resolve an intrinsic
853+
size, assume the size of the first fragmentainer defining a fragmentation context.
854+
</li>
855855
<li>
856856
Fragments of boxes that began on a previous fragmentainer must obey
857857
placement rules with the additional constraint that fragments must

0 commit comments

Comments
 (0)