[css-break] Clarifications to monolithic breaking, update changes section.

fantasai · fantasai · commit 69a557baea82 · 2015-07-16T17:08:16.000-04:00
diff --git a/css-break/Overview.bs b/css-break/Overview.bs
@@ -543,19 +543,6 @@ Rules for Breaking</h2>
     among the possible breaks that are allowed.
   </p>
 
-  <p>
-    Some content is not fragmentable, for example many types of
-    <a href="http://www.w3.org/TR/CSS21/conform.html#replaced-element">replaced elements</a> [[!CSS21]] (such as images or video),
-    scrollable elements, or a single line of text content.
-    Such content is considered <dfn>monolithic</dfn>:
-    it contains no possible break points.
-    In addition to any content which is not fragmentable,
-    UAs may consider as <i>monolithic</i> any elements with
-    'overflow' set to ''overflow/auto'' or ''overflow/scroll'' and
-    any elements with ''overflow: hidden'' and a non-''height/auto''
-    <a href="http://www.w3.org/TR/css3-writing-modes/#block-size">logical height</a>
-    (and no specified maximum logical height).
-
   <p>
 	To guarantee progress, fragmentainers are assumend to have a minimum
 	<i>block size</i> of 1px regardless of their used size.
@@ -610,28 +597,25 @@ Possible Break Points</h3>
     However, individual break points may be prioritized or de-prioritized
     by using the <a href="#breaking-controls">breaking controls</a>.
 
-  <p id=monolithic-breaking>
-    The UA is not required to fragment the contents of <i>monolithic</i> elements,
-    and may instead slice the element's graphical representation
-    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.
-  </p>
-
-  <p>
-    When fragmenting, if there are no possible break points below the top
-    of the fragmentainer, and not all the content fits, the UA may break anywhere
-    in order to avoid losing content off the edge of the fragmentainer.
-  </p>
-
   <p class="note">
     Other layout models may add breakpoints to the above classes.
     For example, [[CSS3-FLEXBOX]] adds certain points within a flex formatting context
     to classes A and C.
   </p>
 
+  <p>
+    Some content is not fragmentable, for example many types of
+    <a href="http://www.w3.org/TR/CSS21/conform.html#replaced-element">replaced elements</a> [[!CSS21]] (such as images or video),
+    scrollable elements, or a single line of text content.
+    Such content is considered <dfn>monolithic</dfn>:
+    it contains no possible break points.
+    In addition to any content which is not fragmentable,
+    UAs may consider as <i>monolithic</i> any elements with
+    'overflow' set to ''overflow/auto'' or ''overflow/scroll'' and
+    any elements with ''overflow: hidden'' and a non-''height/auto''
+    <a href="http://www.w3.org/TR/css3-writing-modes/#block-size">logical height</a>
+    (and no specified maximum logical height).
+
 <h3 id="break-types">
 Types of Breaks</h3>
 
@@ -762,6 +746,16 @@ Unforced Breaks</h3>
   <p class="issue">This means that 'widows' and 'orphans' restrictions
   are given priority over the 'break-*' controls. Is this appropriate?
 
+  <p>
+    Finally, if there are no possible break points below the top of the fragmentainer,
+    and not all the content fits, the UA may break anywhere
+    in order to avoid losing content off the edge of the fragmentainer.
+    <span id="monolithic-breaking">
+    In such cases, the UA may also fragment the contents of <i>monolithic</i> elements
+    by slicing the element's graphical representation.
+  </p>
+
+
 <h3 id="best-breaks">
 Optimizing Unforced Breaks</h3>
 
@@ -1208,12 +1202,12 @@ Transforms, Positioning, and Pagination</h3>
 Changes</h2>
 
   <p>The following significant changes were made since the
-    <a href="http://www.w3.org/TR/2014/WD-css3-break-20140116/">16 January 2014 Working Draft</a>:
+    <a href="http://www.w3.org/TR/2015/WD-css3-break-20150129/">29 January 2015 Working Draft</a>:
 
   <ul>
-    <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.
+    <li>Defined that margins are also cloned for ''box-decoration-break: clone''.
+    <li>Corrected unforced breaking rules (Class A) to handle new break types
+        (original rules only handled page breaks).
   </ul>
 
 <h2 class="no-num" id="acknowledgments">
diff --git a/css-break/Overview.html b/css-break/Overview.html
@@ -1047,20 +1047,6 @@ <h2 class="heading settled" data-level="4" id="breaking-rules"><span class="secn
   </p>
 
   
-   <p>
-    Some content is not fragmentable, for example many types of
-    <a href="http://www.w3.org/TR/CSS21/conform.html#replaced-element">replaced elements</a> <a data-link-type="biblio" href="#biblio-css21">[CSS21]</a> (such as images or video),
-    scrollable elements, or a single line of text content.
-    Such content is considered <dfn data-dfn-type="dfn" data-noexport="" id="monolithic">monolithic<a class="self-link" href="#monolithic"></a></dfn>:
-    it contains no possible break points.
-    In addition to any content which is not fragmentable,
-    UAs may consider as <a data-link-type="dfn" href="#monolithic">monolithic</a> any elements with
-    <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-overflow-3/#propdef-overflow">overflow</a> set to <a class="css" data-link-type="maybe" href="http://dev.w3.org/csswg/css-overflow-3/#valdef-overflow-auto">auto</a> or <a class="css" data-link-type="maybe" href="http://dev.w3.org/csswg/css-overflow-3/#valdef-overflow-scroll">scroll</a> and
-    any elements with <a class="css" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-overflow-3/#propdef-overflow">overflow: hidden</a> and a non-<span class="css">auto</span>
-    <a href="http://www.w3.org/TR/css3-writing-modes/#block-size">logical height</a>
-    (and no specified maximum logical height).
-
-  </p>
    <p>
 	To guarantee progress, fragmentainers are assumend to have a minimum
 	<a data-link-type="dfn" href="http://dev.w3.org/csswg/css-writing-modes-3/#block-size">block size</a> of 1px regardless of their used size.
@@ -1143,31 +1129,27 @@ <h3 class="heading settled" data-level="4.1" id="possible-breaks"><span class="s
     by using the <a href="#breaking-controls">breaking controls</a>.
 
   </p>
-   <p id="monolithic-breaking">
-    The UA is not required to fragment the contents of <a data-link-type="dfn" href="#monolithic">monolithic</a> elements,
-    and may instead slice the element’s graphical representation
-    as necessary to fragment it.
-    In this case it must treat the element as having <a class="css" data-link-type="propdesc" href="#propdef-break-inside">break-inside: avoid</a>,
-    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.
-  </p>
-
-  
-   <p>
-    When fragmenting, if there are no possible break points below the top
-    of the fragmentainer, and not all the content fits, the UA may break anywhere
-    in order to avoid losing content off the edge of the fragmentainer.
-  </p>
-
-  
    <p class="note" role="note">
     Other layout models may add breakpoints to the above classes.
     For example, <a data-link-type="biblio" href="#biblio-css3-flexbox">[CSS3-FLEXBOX]</a> adds certain points within a flex formatting context
     to classes A and C.
   </p>
 
+  
+   <p>
+    Some content is not fragmentable, for example many types of
+    <a href="http://www.w3.org/TR/CSS21/conform.html#replaced-element">replaced elements</a> <a data-link-type="biblio" href="#biblio-css21">[CSS21]</a> (such as images or video),
+    scrollable elements, or a single line of text content.
+    Such content is considered <dfn data-dfn-type="dfn" data-noexport="" id="monolithic">monolithic<a class="self-link" href="#monolithic"></a></dfn>:
+    it contains no possible break points.
+    In addition to any content which is not fragmentable,
+    UAs may consider as <a data-link-type="dfn" href="#monolithic">monolithic</a> any elements with
+    <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-overflow-3/#propdef-overflow">overflow</a> set to <a class="css" data-link-type="maybe" href="http://dev.w3.org/csswg/css-overflow-3/#valdef-overflow-auto">auto</a> or <a class="css" data-link-type="maybe" href="http://dev.w3.org/csswg/css-overflow-3/#valdef-overflow-scroll">scroll</a> and
+    any elements with <a class="css" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-overflow-3/#propdef-overflow">overflow: hidden</a> and a non-<span class="css">auto</span>
+    <a href="http://www.w3.org/TR/css3-writing-modes/#block-size">logical height</a>
+    (and no specified maximum logical height).
 
+</p>
    <h3 class="heading settled" data-level="4.2" id="break-types"><span class="secno">4.2. </span><span class="content">
 Types of Breaks</span><a class="self-link" href="#break-types"></a></h3>
 
@@ -1346,7 +1328,18 @@ <h3 class="heading settled" data-level="4.4" id="unforced-breaks"><span class="s
    <p class="issue" id="issue-bc51c50f"><a class="self-link" href="#issue-bc51c50f"></a>This means that <a class="property" data-link-type="propdesc" href="#propdef-widows">widows</a> and <a class="property" data-link-type="propdesc" href="#propdef-orphans">orphans</a> restrictions
   are given priority over the <a class="property" data-link-type="propdesc">break-*</a> controls. Is this appropriate?
 
-</p>
+  </p>
+   <p>
+    Finally, if there are no possible break points below the top of the fragmentainer,
+    and not all the content fits, the UA may break anywhere
+    in order to avoid losing content off the edge of the fragmentainer.
+    <span id="monolithic-breaking">
+    In such cases, the UA may also fragment the contents of <a data-link-type="dfn" href="#monolithic">monolithic</a> elements
+    by slicing the element’s graphical representation.
+  </span></p>
+
+
+
    <h3 class="heading settled" data-level="4.5" id="best-breaks"><span class="secno">4.5. </span><span class="content">
 Optimizing Unforced Breaks</span><a class="self-link" href="#best-breaks"></a></h3>
 
@@ -1956,16 +1949,15 @@ <h2 class="no-num heading settled" id="changes"><span class="content">
 
   
    <p>The following significant changes were made since the
-    <a href="http://www.w3.org/TR/2014/WD-css3-break-20140116/">16 January 2014 Working Draft</a>:
+    <a href="http://www.w3.org/TR/2015/WD-css3-break-20150129/">29 January 2015 Working Draft</a>:
 
   </p>
    <ul>
     
-    <li>Clarified behavior of fragmented transformed overflow.
-    
-    <li>Clarified the behavior of fragmented <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-backgrounds-3/#border-radius">border-radius</a> curves.
+    <li>Defined that margins are also cloned for <a class="css" data-link-type="propdesc" href="#propdef-box-decoration-break">box-decoration-break: clone</a>.
     
-    <li>Generalized "break anywhere to avoid overflow" rule to all fragmentation types.
+    <li>Corrected unforced breaking rules (Class A) to handle new break types
+        (original rules only handled page breaks).
   
    </ul>
 
@@ -2212,7 +2204,7 @@ <h3 class="no-num heading settled" id="index-defined-here"><span class="content"
    <li>fragmented flow, <a href="#fragmented-flow">2</a>
    <li>left, <a href="#valdef-break-before-left">3.1</a>
    <li>line break, <a href="#line-break">4.2</a>
-   <li>monolithic, <a href="#monolithic">4</a>
+   <li>monolithic, <a href="#monolithic">4.1</a>
    <li>orphans, <a href="#propdef-orphans">3.3</a>
    <li>page, <a href="#valdef-break-before-page">3.1</a>
    <li>page break, <a href="#page-break">4.2</a>
@@ -2418,6 +2410,6 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
    <div class="issue">This means that <a class="property" data-link-type="propdesc" href="#propdef-widows">widows</a> and <a class="property" data-link-type="propdesc" href="#propdef-orphans">orphans</a> restrictions
   are given priority over the <a class="property" data-link-type="propdesc">break-*</a> controls. Is this appropriate?
 
-<a href="#issue-bc51c50f"> ↵ </a></div>
+  <a href="#issue-bc51c50f"> ↵ </a></div>
   </div></body>
 </html>
diff --git a/css-break/issues-lc-2015.txt b/css-break/issues-lc-2015.txt
@@ -2,7 +2,7 @@ Draft:    http://www.w3.org/TR/2015/WD-css3-break-20150129/
 Title:    CSS Fragmentation Level 3
 
 ----
-Issue 2.
+Issue 1.
 Summary:  Clarify slicing requirements for monolithic elements
 From:     Håkon Wium Lie
 Comment:  http://www.w3.org/mid/21703.26184.790775.276339@opera.com
@@ -39,16 +39,16 @@ Resolved:
 Issue 5.
 Summary:  Grammatical errors
 From:     Brady Duga  
-Comment:  http://www.w3.org/mid/CAKpG1kH+JX=fWrcTb_vKhnbPfR5YaNWpaichmLkCoQoMJxh94w@mail.gmail.com
-Response: 
+Comment:  https://lists.w3.org/Archives/Public/www-style/2015Mar/0380.html
+Response: https://lists.w3.org/Archives/Public/www-style/2015May/0214.html
 Closed:   Accepted
 Resolved: Editorial
 ----
 Issue 6.
 Summary:  Confusion on break types wrt nested flows
 From:     Brady Duga
 Comment:  http://www.w3.org/mid/CAKpG1kGBU1qNTLsM0xhBesEYCfY+ABbZY2SbTU-e+2HeA9X5Ug@mail.gmail.com
-Response: 
+Response: https://lists.w3.org/Archives/Public/www-style/2015May/0218.html
 Closed:   Accepted
 Resolved: Editorial
 ----
@@ -64,32 +64,33 @@ Issue 8.
 Summary:  Multiple principal boxes problematic
 From:     Brady Duga
 Comment:  http://www.w3.org/mid/CAKpG1kEp8+sfnrNkbuab5sH=HnPiPv3MHg5SQ8Ou=OK1iXy7Hw@mail.gmail.com
-Response: 
+Response: https://lists.w3.org/Archives/Public/www-style/2015May/0215.html
 Closed:   Invalid
 Resolved: Editor's discretion
 ----
 Issue 9.
 Summary:  Page progression undefined
 From:     Brady Duga
 Comment:  http://www.w3.org/mid/CAKpG1kG-TbN_pbHY_4QdvdauiG8=nrTu1NEx56vTaGNcWUxaRw@mail.gmail.com
-Response: 
+Response: https://lists.w3.org/Archives/Public/www-style/2015May/0216.html
 Closed:   Accepted
 Resolved: Editorial
 ----
 Issue 10.
 Summary:  Multiple avoidances
 From:     Brady Duga
 Comment:  http://www.w3.org/mid/CAKpG1kGQucyO-9x=zK4d1u=hK1C_yGrn9yhAJf+SGuYPm37W-w@mail.gmail.com
-Response: 
-Open
-Resolved: =Agenda=
+Response: https://lists.w3.org/Archives/Public/www-style/2015May/0217.html
+Response: https://lists.w3.org/Archives/Public/www-style/2015Jul/0228.html
+Closed:   Deferred
+Resolved: https://lists.w3.org/Archives/Public/www-style/2015May/0279.html
 ----
 Issue 11.
 Summary:  Breaking rules too specifically defined
 From:     Brady Duga
 Comment:  http://www.w3.org/mid/CAKpG1kFESW0OmVKi8qJ7FGKPG9g1+h-f2rW6JqxFBawrH+4Egw@mail.gmail.com
-Response: 
-Open
+Response: https://lists.w3.org/Archives/Public/www-style/2015Jul/0229.html
+Closed:   Accepted
 Resolved: Bugfix
 ----
 Issue 12.
@@ -104,8 +105,11 @@ Issue 13.
 Summary:  box-decoration-break and margins
 From:     Håkon Wium Lie
 Comment:  http://www.w3.org/mid/826769891.862609.1428367549875.JavaMail.yahoo@mail.yahoo.com%28sfid-20150407_103540_382741_CD8ECAC2%29
-Response: 
+Response: https://lists.w3.org/Archives/Public/www-style/2015Jul/0230.html
 Open
 Resolved: =Agenda=
 ----
-
+Issue 14.
+Summary:  Drop cloned margins/padding/border if running out of space
+From:     Rossen Atanassov
+Comment:  https://lists.w3.org/Archives/Public/www-style/2015May/0279.html
