@@ -686,12 +686,13 @@ Flex Item Margins and Paddings</h3>
686
686
687
687
Percentage margins and paddings on <a>flex items</a> can be resolved against either:
688
688
689
- 1. their own axis (left/right percentages resolve against width, top/bottom resolve against height)
690
- 2. the inline axis (left/right/top/bottom percentages all resolve against width)
689
+ * their own axis (left/right percentages resolve against width, top/bottom resolve against height), or,
690
+ * the inline axis (left/right/top/bottom percentages all resolve against width)
691
691
692
692
A User Agent must choose one of these two behaviors.
693
693
694
- Note: This behavior sucks, but it accurately captures the current state of the world.
694
+ Note: This variance sucks, but it accurately captures the current state of the world
695
+ (no consensus among implementations, and no consensus within the CSSWG).
695
696
It is the CSSWG's intention that browsers will converge on one of the behaviors,
696
697
at which time the spec will be amended to require that.
697
698
@@ -2859,6 +2860,11 @@ Fragmenting Flex Layout</h2>
2859
2860
If as a result of this adjustment the available space becomes negative,
2860
2861
it is set to zero.
2861
2862
2863
+ <li>
2864
+ If the first fragment of the flex container is not at the top of the page,
2865
+ and none of its flex items fit in the remaining space on the page,
2866
+ the entire fragment is moved to the next page.
2867
+
2862
2868
<li>
2863
2869
When a <a>multi-line</a> column flex container breaks,
2864
2870
each fragment has its own "stack" of flex lines,
0 commit comments