[css-break] Fold in some clarifications. Make monolithic elements respect 'slice to avoid overflow' rule.

Author: fantasai

css-break/Overview.html

@@ -13,7 +13,7 @@
    rel=dcterms.rights>
   <meta content="CSS Fragmentation Module Level 3" name=dcterms.title>
   <meta content=text name=dcterms.type>
-  <meta content=2015-01-19 name=dcterms.date>
+  <meta content=2015-01-20 name=dcterms.date>
   <meta content="Rossen Atanassov" name=dcterms.creator>
   <meta content="Microsoft Corporation" name=dcterms.creator>
   <meta
@@ -26,7 +26,7 @@
   <link href="../default.css" rel=stylesheet type="text/css">
   <link href="http://www.w3.org/StyleSheets/TR/W3C-ED.css" rel=stylesheet
    type="text/css">
-  <style>
+  <style type=css>
     .css::before, .css::after, .property::before, .property::after { content: none !important;}
   </style>
 
@@ -40,7 +40,7 @@ <h1 id=css-fragmentation-module>CSS Fragmentation Module Level 3</h1>
    <h2 class="no-num no-toc" id=subtitle>Breaking the Web, one fragment at a
     time</h2>
 
-   <h2 class="no-num no-toc">Editor's Draft 19 January 2015</h2>
+   <h2 class="no-num no-toc">Editor's Draft 20 January 2015</h2>
 
    <dl>
     <dt>This version:
@@ -371,8 +371,11 @@ <h2 id=fragmentation-model><span class=secno>2. </span> Fragmentation Model
     chain of <a href="http://www.w3.org/TR/css3-regions">CSS regions</a>, or
     a <a href="http://www.w3.org/TR/css3-page/">paged media display</a>. A
     given fragmentation context can only have one block flow direction across
-    all its <a href="#fragmentainer"><i>fragmentainers</i></a>.
-    <!-- XXX clarify that multiple writing modes are allowed, just fragmentationis in one direction -->
+    all its <a href="#fragmentainer"><i>fragmentainers</i></a>. (Descendants
+    of the <a href="#fragmentation-root"><i>fragmentation root</i></a> may
+    have other block flow directions, but fragmentation proceeds according to
+    the block flow direction applied to the <a
+    href="#fragmentation-root"><i>fragmentation root</i></a>.)
 
    <dt><dfn id=fragmented-flow>fragmented flow</dfn>
 
@@ -458,11 +461,12 @@ <h3 id=parallel-flows><span class=secno>2.1. </span> Parallel Fragmentation
   </ul>
 
   <p> Content overflowing the content edge of a fixed-size box is considered
-   parallel to the content after the fixed-size box. Such content fragments
-   within the context of the box's <a href="#fragmented-flow"><i>fragmented
-   flow</i></a> following normal fragmentation rules, increasing the length
-   of the <a href="#fragmented-flow"><i>fragmented flow</i></a> as necessary.
-   <!-- XXX this paragraph is generally confusing -->
+   parallel to the content after the fixed-size box and follows the normal
+   fragmentation rules. Although overflowing content doesn't affect the size
+   of the <a href="#fragmentation-root"><i>fragmentation root</i></a> box, it
+   does increase the length of the <a href="#fragmented-flow"><i>fragmented
+   flow</i></a>, spilling into or generating additional <a
+   href="#fragmentainer"><i>fragmentainers</i></a> as necessary.
 
   <h3 id=nested-flows><span class=secno>2.2. </span> Nested Fragmentation
    Flows</h3>
@@ -938,10 +942,11 @@ <h3 id=possible-breaks><span class=secno>4.1. </span> Possible Break Points</h3>
      <dt>Block-parallel Fragmentation
 
      <dd> When the block flow direction of the siblings' containing block is
-      parallel to that of the fragmentation context: in-flow block-level
-      boxes, <!-- XXX linkify in-flow --> a float and an immediately-adjacent
-      in-flow or floated box, table row group boxes, table row boxes,
-      multi-column column row boxes.
+      parallel to that of the fragmentation context: <a
+      href="http://www.w3.org/TR/2011/REC-CSS2-20110607/visuren.html#positioning-scheme">in-flow</a>
+      block-level boxes, a float and an immediately-adjacent in-flow or
+      floated box, table row group boxes, table row boxes, multi-column
+      column row boxes.
 
      <dt>Block-perpendicular Fragmentation
 
@@ -965,13 +970,12 @@ <h3 id=possible-breaks><span class=secno>4.1. </span> Possible Break Points</h3>
   <p class=note> There is no inherent prioritization among these classes of
    break points. However, individual break points may be prioritized or
    de-prioritized by using the <a href="#breaking-controls">breaking
-   controls</a>. <!-- XXX fix this, it's inconsistent -->
+   controls</a>.
 
   <p id=monolithic-breaking> The UA is not required to fragment the contents
    of <a href="#monolithic"><i>monolithic</i></a> elements, and may instead
    either slice the element's graphical representation as necessary to
-   fragment it or treat its box as unbreakable and overflow the
-   fragmentainer. In both cases it must treat the element as having ‘<code
+   fragment it. In this case it must treat the element as having ‘<code
    class=css>break-inside: avoid</code>’, i.e. only slice or overflow at
    the fragmentainer edge if there are no other <a
    href="#possible-breaks">possible break points</a> in the fragmentainer.
@@ -1753,38 +1757,17 @@ <h3 id=cr-exit-criteria><span class=secno>6.6. </span> CR Exit Criteria</h3>
   <h2 class=no-num id=changes> Changes</h2>
 
   <p>The following significant changes were made since the <a
-   href="http://www.w3.org/TR/2012/WD-css3-break-20120823/">29 August 2012
+   href="http://www.w3.org/TR/2014/WD-css3-break-20140116/">16 January 2014
    Working Draft</a>:
 
   <ul>
-   <li>Added definition of ‘<a href="#box-decoration-break"><code
-    class=property>box-decoration-break</code></a>’ (moved from <a
-    href="#ref-CSS3BG" rel=biblioentry>[CSS3BG]<!--{{CSS3BG}}--></a>) and
-    defined better handling of aspect-ratio-sized images in variable-sized
-    fragments.
+   <li>Clarified behavior of fragmented transformed overflow.
 
-   <li>Added ‘<a href="#any"><code class=css>any</code></a>’ value to
-    ‘<a href="#break-before"><code
-    class=property>break-before</code></a>’ and ‘<a
-    href="#break-after"><code class=property>break-after</code></a>’.
+   <li>Clarified the behavior of fragmented ‘<code
+    class=property>border-radius</code>’ curves.
 
-   <li>Defined that boxes <a href="#box-splitting">extend to the bottom of
-    the page</a> when broken.
-
-   <li>Defined breaking of <a href="#transforms">transformed/positioned
-    content</a>.
-
-   <li>Defined 1px minimum extent of fragmentainers to ensure progress.
-
-   <li>Clarified fragmentation of <a href="#parallel-flows">parallel
-    flows</a>.
-
-   <li>Defined handling of overflowing content (as parallel content).
-
-   <li>Clarified <a href="#varying-size-boxes">float fragmentation</a> in
-    varying-size fragmentainers.
-
-   <li>Various other clarifications.
+   <li>Generalized "break anywhere to avoid overflow" rule to all
+    fragmentation types.
   </ul>
 
   <h2 class=no-num id=acknowledgments> Acknowledgments</h2>

css-break/Overview.src.html

@@ -7,7 +7,7 @@
   <title>CSS Fragmentation Module Level 3</title>
   <link rel="stylesheet" type="text/css" href="../default.css">
   <link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED.css">
-  <style>
+  <style type=css>
     .css::before, .css::after, .property::before, .property::after { content: none !important;}
   </style>
 </head>
@@ -148,7 +148,8 @@ <h2 id="fragmentation-model">
       or a <a href="http://www.w3.org/TR/css3-page/">paged media display</a>.
       A given fragmentation context can only have one block flow direction
       across all its <i>fragmentainers</i>.
-      <!-- XXX clarify that multiple writing modes are allowed, just fragmentationis in one direction -->
+      (Descendants of the <i>fragmentation root</i> may have other block flow directions,
+      but fragmentation proceeds according to the block flow direction applied to the <i>fragmentation root</i>.)
     </dd>
     <dt><dfn>fragmented flow</dfn></dt>
     <dd>
@@ -223,11 +224,11 @@ <h3 id="parallel-flows">
 
   <p>
     Content overflowing the content edge of a fixed-size box
-    is considered parallel to the content after the fixed-size box.
-    Such content fragments within the context of the box's <i>fragmented flow</i>
-    following normal fragmentation rules,
-    increasing the length of the <i>fragmented flow</i> as necessary.
-    <!-- XXX this paragraph is generally confusing -->
+    is considered parallel to the content after the fixed-size box
+    and follows the normal fragmentation rules.
+    Although overflowing content doesn't affect the size of the <i>fragmentation root</i> box,
+    it does increase the length of the <i>fragmented flow</i>,
+    spilling into or generating additional <i>fragmentainers</i> as necessary.
   </p>
 
 <h3 id="nested-flows">
@@ -626,7 +627,7 @@ <h3 id="possible-breaks">
         <dd>
           When the block flow direction of the siblings' containing block
           is parallel to that of the fragmentation context:
-          in-flow block-level boxes, <!-- XXX linkify in-flow -->
+          <a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/visuren.html#positioning-scheme">in-flow</a> block-level boxes,
           a float and an immediately-adjacent in-flow or floated box,
           table row group boxes,
           table row boxes,
@@ -660,14 +661,11 @@ <h3 id="possible-breaks">
     However, individual break points may be prioritized or de-prioritized
     by using the <a href="#breaking-controls">breaking controls</a>.
 
-<!-- XXX fix this, it's inconsistent -->
-
   <p id=monolithic-breaking>
     The UA is not required to fragment the contents of <i>monolithic</i> elements,
     and may instead either slice the element's graphical representation
-    as necessary to fragment it
-    or treat its box as unbreakable and overflow the fragmentainer.
-    In both cases it must treat the element as having ''break-inside: avoid'',
+    as necessary to fragment it.
+    In this case it must treat the element as having ''break-inside: avoid'',
     i.e. only slice or overflow at the fragmentainer edge
     if there are no other <a href="#possible-breaks">possible break points</a>
     in the fragmentainer.
@@ -1417,19 +1415,12 @@ <h2 class="no-num" id="changes">
 Changes</h2>
 
   <p>The following significant changes were made since the
-    <a href="http://www.w3.org/TR/2012/WD-css3-break-20120823/">29 August 2012 Working Draft</a>:
+    <a href="http://www.w3.org/TR/2014/WD-css3-break-20140116/">16 January 2014 Working Draft</a>:
 
   <ul>
-    <li>Added definition of 'box-decoration-break' (moved from [[CSS3BG]])
-      and defined better handling of aspect-ratio-sized images in variable-sized fragments.
-    <li>Added ''any'' value to 'break-before' and 'break-after'.
-    <li>Defined that boxes <a href="#box-splitting">extend to the bottom of the page</a> when broken.
-    <li>Defined breaking of <a href="#transforms">transformed/positioned content</a>.
-    <li>Defined 1px minimum extent of fragmentainers to ensure progress.
-    <li>Clarified fragmentation of <a href="#parallel-flows">parallel flows</a>.
-    <li>Defined handling of overflowing content (as parallel content).
-    <li>Clarified <a href="#varying-size-boxes">float fragmentation</a> in varying-size fragmentainers.
-    <li>Various other clarifications.
+    <li>Clarified behavior of fragmented transformed overflow.
+    <li>Clarified the behavior of fragmented 'border-radius' curves.
+    <li>Generalized "break anywhere to avoid overflow" rule to all fragmentation types.
   </ul>
 
 <h2 class="no-num" id="acknowledgments">