[css-break] Notes to self

Author: fantasai

css-break/Overview.src.html

@@ -140,6 +140,7 @@ <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 -->
     </dd>
     <dt><dfn>fragmented flow</dfn></dt>
     <dd>
@@ -218,6 +219,7 @@ <h3 id="parallel-flows">
     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 -->
   </p>
 
 <h3 id="nested-flows">
@@ -604,7 +606,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,
+          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,
@@ -629,6 +631,7 @@ <h3 id="possible-breaks">
       child content (margin edges of block-level children or line box
       edges for inline-level children) <em>if</em> there is a (non-zero)
       gap between them.
+      <!-- XXX add example -->
     </dd>
   </dl>
 
@@ -652,6 +655,7 @@ <h3 id="possible-breaks">
     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>
 
   <p class="note">
@@ -786,6 +790,9 @@ <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.
+
 <h3 id="best-breaks">
 Optimizing Unforced Breaks</h3>
 
@@ -859,6 +866,7 @@ <h3 id="varying-size-boxes">
     When a flow is fragmented into varying-size fragmentainers, the following
     rules are observed for adapting layout:
   </p>
+  <!-- try to make this clearer. Steve suggests swapping first two points, maybe break it up more? -->
   <ul>
     <li>
       Intrinsic sizes are calculated and maintained across the entire element.