Add Alan Stearn's issue about propagating column breaks up to pages, etc, along with some proposed text

Author: fantasai

css3-break/Overview.html

@@ -904,6 +904,15 @@ <h3 id=forced-breaks><span class=secno>4.3. </span> Forced breaks</h3>
    class=property>page</code>’. See <a href="#CSS3PAGE"
    rel=biblioentry>[CSS3PAGE]<!--{{!CSS3PAGE}}--></a>
 
+  <p class=issue> <a
+   href="http://lists.w3.org/Archives/Public/www-style/2012Aug/0319.html">Issue:</a>
+   When a forced break occurs, it forces ensuing content into the next
+   fragmenter of the type associated with the break, breaking through as many
+   fragmentation contexts as necessary until the specified break types are
+   all satisfied. If the document is not fragmented (e.g. in continous media
+   when no fragmenting features such as multi-column layout are used), then
+   the forced break has no effect.
+
   <h3 id=unforced-breaks><span class=secno>4.4. </span> Unforced Breaks</h3>
 
   <p> While <a href="#breaking-controls">breaking controls</a> can force

css3-break/Overview.src.html

@@ -640,6 +640,15 @@ <h3 id="forced-breaks">
     if the last line box above this margin and the first one below it do not have the
     same value for 'page'. See [[!CSS3PAGE]]
   </p>
+  <p class="issue">
+    <a href="http://lists.w3.org/Archives/Public/www-style/2012Aug/0319.html">Issue:</a>
+    When a forced break occurs,
+    it forces ensuing content into the next fragmenter of the type associated with the break,
+    breaking through as many fragmentation contexts as necessary
+    until the specified break types are all satisfied.
+    If the document is not fragmented
+    (e.g. in continous media when no fragmenting features such as multi-column layout are used),
+    then the forced break has no effect.
 
 <h3 id="unforced-breaks">
 Unforced Breaks</h3>