[css-break] Clarify that overflowing content is a parallel fragmentation flow. <http://lists.w3.org/Archives/Public/www-style/2013Oct/0339.html>

Author: fantasai

css-break/Overview.html

@@ -163,6 +163,13 @@ <h2 class="no-num no-toc" id=contents> Table of contents</h2>
 
    <li><a href="#fragmentation-model"><span class=secno>2. </span>
     Fragmentation Model and Terminology</a>
+    <ul class=toc>
+     <li><a href="#parallel-flows"><span class=secno>2.1. </span> Parallel
+      Fragmentation Flows</a>
+
+     <li><a href="#nested-flows"><span class=secno>2.2. </span> Nested
+      Fragmentation Flows</a>
+    </ul>
 
    <li><a href="#breaking-controls"><span class=secno>3. </span> Controlling
     Breaks</a>
@@ -403,12 +410,50 @@ <h2 id=fragmentation-model><span class=secno>2. </span> Fragmentation Model
    new <a href="#fragmentainer"><i>fragmentainer</i></a> to be generated to
    hold the deferred content.
 
-  <p> When multiple flows are laid out in parallel, fragmentation is
-   performed independently in each flow. For example, if an element is
+  <p class=note> Breaking inline content into lines is another form of
+   fragmentation, and similarly creates box fragments when it breaks <a
+   href="http://www.w3.org/TR/CSS21/visuren.html#inline-boxes">inline
+   boxes</a> across <a
+   href="http://www.w3.org/TR/CSS21/visuren.html#line-box">line boxes</a>.
+   However, inline breaking is not covered here; see [CSS21]]/<a
+   href="#ref-CSS3TEXT" rel=biblioentry>[CSS3TEXT]<!--{{CSS3TEXT}}--></a>.
+
+  <h3 id=parallel-flows><span class=secno>2.1. </span> Parallel Fragmentation
+   Flows</h3>
+
+  <p> When multiple flows are laid out parallel to each other, fragmentation
+   is performed independently in each flow. For example, if an element is
    floated, then a forced break inside the float will not affect the content
    wrapping outside the float (except insofar as it may increase the height
    of the float).
 
+  <p> The following are examples of parallel flows whose contents will
+   fragment independently:
+
+  <ul>
+   <li>The contents of a float vs. the content wrapping outside the float.
+
+   <li>The contents of a float vs. the contents of an adjacent float.
+
+   <li>The contents of each table cell in a single table row.
+
+   <li>The contents of each grid item in a single grid row.
+
+   <li>The contents of each flex item in a flex layout row.
+
+   <li>The contents of absolutely-positioned elements that cover the same
+    range of their containing block's fragmentation context.
+  </ul>
+
+  <p> Content overflowing the content edge of a fixed-size box is considered
+   parallel to the content after the fixed-size box. Note however that
+   content <em>not</em> overflowing the content edge of a fixed-size box is
+   embedded within the same flow as the in-flow content after it. (The
+   content edge effectively forks the fragmentation.)
+
+  <h3 id=nested-flows><span class=secno>2.2. </span> Nested Fragmentation
+   Flows</h3>
+
   <p> Breaking a <a href="#fragmentainer"><i>fragmentainer</i></a>
    <var>F</var> effectively splits the <a
    href="#fragmentainer"><i>fragmentainer</i></a> into two <a
@@ -421,14 +466,6 @@ <h2 id=fragmentation-model><span class=secno>2. </span> Fragmentation Model
    created by <var>F</var>’s own <a
    href="#fragmentation-context"><i>fragmentation context</i></a>.
 
-  <p class=note> Breaking inline content into lines is another form of
-   fragmentation, and similarly creates box fragments when it breaks <a
-   href="http://www.w3.org/TR/CSS21/visuren.html#inline-boxes">inline
-   boxes</a> across <a
-   href="http://www.w3.org/TR/CSS21/visuren.html#line-box">line boxes</a>.
-   However, inline breaking is not covered here; see <a href="#ref-CSS3TEXT"
-   rel=biblioentry>[CSS3TEXT]<!--{{CSS3TEXT}}--></a>.
-
   <h2 id=breaking-controls><span class=secno>3. </span> Controlling Breaks</h2>
 
   <p> The following sections explain how breaks are controlled in a <a

css-break/Overview.src.html

@@ -177,15 +177,51 @@ <h2 id="fragmentation-model">
     to hold the deferred content.
   </p>
 
+  <p class="note">
+    Breaking inline content into lines is another form of fragmentation,
+    and similarly creates box fragments when it breaks
+    <a href="http://www.w3.org/TR/CSS21/visuren.html#inline-boxes">inline boxes</a>
+    across <a href="http://www.w3.org/TR/CSS21/visuren.html#line-box">line boxes</a>.
+    However, inline breaking is not covered here; see [CSS21]]/[[CSS3TEXT]].
+  </p>
+
+<h3 id="parallel-flows">
+Parallel Fragmentation Flows</h3>
+
   <p>
-    When multiple flows are laid out in parallel,
+    When multiple flows are laid out parallel to each other,
     fragmentation is performed independently in each flow.
     For example, if an element is floated,
     then a forced break inside the float
     will not affect the content wrapping outside the float
     (except insofar as it may increase the height of the float).
   </p>
 
+  <p>
+    The following are examples of parallel flows
+    whose contents will fragment independently:
+  </p>
+  <ul>
+    <li>The contents of a float vs. the content wrapping outside the float.
+    <li>The contents of a float vs. the contents of an adjacent float.
+    <li>The contents of each table cell in a single table row.
+    <li>The contents of each grid item in a single grid row.
+    <li>The contents of each flex item in a flex layout row.
+    <li>The contents of absolutely-positioned elements
+        that cover the same range of their containing block's fragmentation context.
+  </ul>
+
+  <p>
+    Content overflowing the content edge of a fixed-size box
+    is considered parallel to the content after the fixed-size box.
+    Note however that content <em>not</em> overflowing the content edge of a fixed-size box
+    is embedded within the same flow as the in-flow content after it.
+    (The content edge effectively forks the fragmentation.)
+  </p>
+
+<h3 id="nested-flows">
+Nested Fragmentation Flows</h3>
+
   <p>
     Breaking a <i>fragmentainer</i> <var>F</var> effectively splits the <i>fragmentainer</i>
     into two <i>fragmentainers</i> (<var>F<sub>1</sub></var> and <var>F<sub>2</sub></var>).
@@ -196,14 +232,6 @@ <h2 id="fragmentation-model">
     not the type of break normally created by <var>F</var>’s own <i>fragmentation context</i>.
   </p>
 
-  <p class="note">
-    Breaking inline content into lines is another form of fragmentation,
-    and similarly creates box fragments when it breaks
-    <a href="http://www.w3.org/TR/CSS21/visuren.html#inline-boxes">inline boxes</a>
-    across <a href="http://www.w3.org/TR/CSS21/visuren.html#line-box">line boxes</a>.
-    However, inline breaking is not covered here; see [[CSS3TEXT]].
-  </p>
-
 <h2 id="breaking-controls">
 Controlling Breaks</h2>