[css-break] Resolve last issue. Mark other question as an issue so that we get feedback on it (hopefully).

Author: fantasai

css-break/Overview.html

@@ -12,7 +12,7 @@
    rel=dcterms.rights>
   <meta content="CSS Fragmentation Module Level 3" name=dcterms.title>
   <meta content=text name=dcterms.type>
-  <meta content=2014-10-28 name=dcterms.date>
+  <meta content=2014-11-19 name=dcterms.date>
   <meta content="Rossen Atanassov" name=dcterms.creator>
   <meta content="Microsoft Corporation" name=dcterms.creator>
   <meta
@@ -36,7 +36,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 28 October 2014</h2>
+   <h2 class="no-num no-toc">Editor's Draft 19 November 2014</h2>
 
    <dl>
     <dt>This version:
@@ -305,8 +305,8 @@ <h2 id=intro><span class=secno>1. </span> Introduction</h2>
 
   <p> In CSS, in addition to paged media, certain layout features such as <a
    href="http://www.w3.org/TR/css3-regions/">regions</a> <a
-   href="#ref-CSS3-REGIONS"
-   rel=biblioentry>[CSS3-REGIONS]<!--{{CSS3-REGIONS}}--></a> and <a
+   href="#ref-CSS-REGIONS-1"
+   rel=biblioentry>[CSS-REGIONS-1]<!--{{CSS-REGIONS-1}}--></a> and <a
    href="http://www.w3.org/TR/css3-multicol/">multi-column layout</a> <a
    href="#ref-CSS3COL" rel=biblioentry>[CSS3COL]<!--{{CSS3COL}}--></a> create
    a similarly fragmented environment. The generic term for breaking content
@@ -960,10 +960,10 @@ <h3 id=possible-breaks><span class=secno>4.1. </span> Possible Break Points</h3>
    the fragmentainer edge if there are no <a href="#possible-breaks">possible
    break points</a> on the fragmentainer.
 
-  <p> When paginating, if there are no possible break points below the top of
-   the page, and not all the content fits, the UA may break anywhere in order
-   to avoid losing content off the edge of the page. <span class=issue>Should
-   this be generalized to fragmentainer?</span>
+  <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 class=note> Other layout models may add breakpoints to the above
    classes. For example, <a href="#ref-CSS3-FLEXBOX"
@@ -1004,8 +1004,8 @@ <h3 id=break-types><span class=secno>4.2. </span> Types of Breaks</h3>
    <dd> A break between two <a
     href="http://www.w3.org/TR/css3-regions/#regions">regions</a>. Note that
     if the region boxes are on different pages, then the break is also a <a
-    href="#page-break"><i>page break</i></a>. <a href="#ref-CSS3-REGIONS"
-    rel=biblioentry>[CSS3-REGIONS]<!--{{!CSS3-REGIONS}}--></a>
+    href="#page-break"><i>page break</i></a>. <a href="#ref-CSS-REGIONS-1"
+    rel=biblioentry>[CSS-REGIONS-1]<!--{{!CSS-REGIONS-1}}--></a>
   </dl>
 
   <p class=note> A fifth type of break is the <dfn id=line-break>line
@@ -1105,10 +1105,10 @@ <h3 id=unforced-breaks><span class=secno>4.4. </span> Unforced Breaks</h3>
   <p> If that still does not lead to sufficient break points, rule 3 is
    dropped as well, to find still more break points.
 
-  <p class="note issue">This means that ‘<a href="#widows"><code
+  <p class=issue>This means that ‘<a href="#widows"><code
    class=property>widows</code></a>’ and ‘<a href="#orphans"><code
    class=property>orphans</code></a>’ restrictions are given priority over
-   the ‘<code class=css>break-*</code>’ controls.
+   the ‘<code class=css>break-*</code>’ controls. Is this appropriate?
 
   <h3 id=best-breaks><span class=secno>4.5. </span> Optimizing Unforced
    Breaks</h3>
@@ -1786,6 +1786,16 @@ <h3 class=no-num id=normative-references>Normative references</h3>
    <dd style="display: none"><!-- keeps the doc valid if the DL is empty -->
     <!---->
 
+   <dt id=ref-CSS-REGIONS-1>[CSS-REGIONS-1]
+
+   <dd>Rossen Atanassov; Alan Stearns. <a
+    href="http://www.w3.org/TR/2014/WD-css-regions-1-20141009/"><cite>CSS
+    Regions Module Level 1.</cite></a> 9 October 2014. W3C Working Draft.
+    (Work in progress.) URL: <a
+    href="http://www.w3.org/TR/2014/WD-css-regions-1-20141009/">http://www.w3.org/TR/2014/WD-css-regions-1-20141009/</a>
+   </dd>
+   <!---->
+
    <dt id=ref-CSS21>[CSS21]
 
    <dd>Bert Bos; et al. <a
@@ -1796,16 +1806,6 @@ <h3 class=no-num id=normative-references>Normative references</h3>
    </dd>
    <!---->
 
-   <dt id=ref-CSS3-REGIONS>[CSS3-REGIONS]
-
-   <dd>Rossen Atanassov; Alan Stearns. <a
-    href="http://www.w3.org/TR/2014/WD-css3-regions-20140218/"><cite>CSS
-    Regions Module Level 1.</cite></a> 18 February 2014. W3C Working Draft.
-    (Work in progress.) URL: <a
-    href="http://www.w3.org/TR/2014/WD-css3-regions-20140218/">http://www.w3.org/TR/2014/WD-css3-regions-20140218/</a>
-   </dd>
-   <!---->
-
    <dt id=ref-CSS3-TRANSFORMS>[CSS3-TRANSFORMS]
 
    <dd>Simon Fraser; et al. <a
@@ -1888,10 +1888,10 @@ <h3 class=no-num id=other-references>Other references</h3>
    <dt id=ref-CSS3-FLEXBOX>[CSS3-FLEXBOX]
 
    <dd>Tab Atkins Jr.; fantasai; Rossen Atanassov. <a
-    href="http://www.w3.org/TR/2014/WD-css-flexbox-1-20140325/"><cite>CSS
-    Flexible Box Layout Module Level 1.</cite></a> 25 March 2014. W3C Last
-    Call Working Draft. (Work in progress.) URL: <a
-    href="http://www.w3.org/TR/2014/WD-css-flexbox-1-20140325/">http://www.w3.org/TR/2014/WD-css-flexbox-1-20140325/</a>
+    href="http://www.w3.org/TR/2014/WD-css-flexbox-1-20140925/"><cite>CSS
+    Flexible Box Layout Module Level 1.</cite></a> 25 September 2014. W3C
+    Last Call Working Draft. (Work in progress.) URL: <a
+    href="http://www.w3.org/TR/2014/WD-css-flexbox-1-20140925/">http://www.w3.org/TR/2014/WD-css-flexbox-1-20140925/</a>
    </dd>
    <!---->
 

css-break/Overview.src.html

@@ -655,10 +655,9 @@ <h3 id="possible-breaks">
   </p>
 
   <p>
-    When paginating, if there are no possible break points below the top
-    of the page, and not all the content fits, the UA may break anywhere
-    in order to avoid losing content off the edge of the page.
-    <span class="issue">Should this be generalized to fragmentainer?</span>
+    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">
@@ -793,8 +792,8 @@ <h3 id="unforced-breaks">
     dropped as well, to find still more break points.
   </p>
 
-  <p class="note issue">This means that 'widows' and 'orphans' restrictions
-  are given priority over the 'break-*' controls.
+  <p class="issue">This means that 'widows' and 'orphans' restrictions
+  are given priority over the 'break-*' controls. Is this appropriate?
 
 <h3 id="best-breaks">
 Optimizing Unforced Breaks</h3>