Added note about further layout steps to handle edge cases better

Author: vhardy

css3-regions/Overview.html

@@ -224,13 +224,13 @@
 
    <h1 id=css-regions-module>CSS Regions Module Level 3</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 4 April 2012</h2>
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 6 April 2012</h2>
 
    <dl>
     <dt>This version:
 
     <dd><a
-     href="http://www.w3.org/TR/2012/ED-css3-regions-20120404/">http://www.w3.org/csswg/css3-regions</a>
+     href="http://www.w3.org/TR/2012/ED-css3-regions-20120406/">http://www.w3.org/csswg/css3-regions</a>
 
     <dt>Latest version:
 
@@ -2598,14 +2598,9 @@ <h4 id=regions-boxes-layout><span class=secno>7.2.2. </span>Step 2: regions
    resolution</a> section.
 
   <p>If a measure of the content is required to resolve the used height of
-   the region box (for example if the region box is absolutely positioned),
-   the <span>flow fragment height</span> resolved in Step 1 is used for the
-   vertical content measure of the region.
-
-  <p class=note>The <span>flow fragment height</span> computed in Step 1
-   accounts for the generated content and the RFCB. This is why the content
-   height of the generated content is not used here in addition to the
-   <span>flow fragment height</span>.
+   the RFCB (for example if the region box is absolutely positioned), the
+   <span>flow fragment height</span> resolved in Step 1 is used for the
+   vertical content measure of the RFCB.
 
   <p>At the end of this step, regions are laid out and ready to receive
    content from their associated <a href="#named-flow0">named flows</a>.
@@ -2631,6 +2626,15 @@ <h4 id=named-flows-layout><span class=secno>7.2.3. </span>Step 3: named
   <p>During this phase, generated content is laid out according to the <a
    href="#processing-model">rules</a> described earlier in this document.
 
+  <div class=note>
+   <p>The model for resolving auto sized regions will cause, under certain
+    circumstances, the flow content to be overset or underset. In other
+    words, it will not fit tightly. The model prevents having circular
+    dependencies in the layout model. Implementations may decide to apply
+    further layout steps to ensure that the whole flow content is displayed
+    to the user, even in edge cases.</p>
+  </div>
+
   <h3 id=regions-visual-formatting-implementation-note><span class=secno>7.3.
    </span>Regions visual formatting: implementation note</h3>
 

css3-regions/Overview.src.html

@@ -2095,13 +2095,9 @@ <h4 id="regions-boxes-layout">Step 2: regions boxes layout</h4>
         <a href="#rfbc-width-resolution">RFCB width resolution</a> section.</p>
 
     <p>If a measure of the content
-        is required to resolve the used height of the region box (for example if the region box is absolutely positioned), 
+        is required to resolve the used height of the RFCB (for example if the region box is absolutely positioned), 
         the <span>flow fragment height</span> resolved in Step 1 is used for the vertical content measure of the 
-        region.</p>
-        
-    <p class="note">The <span>flow fragment height</span> computed in Step 1 accounts for the 
-        generated content and the RFCB. This is why the content height of the generated content 
-        is not used here in addition to the <span>flow fragment height</span>.</p>
+        RFCB.</p>
 
     <p>At the end of this step, regions are laid out and ready to receive
     content from their associated <span>named flows</span>.</p>
@@ -2123,6 +2119,14 @@ <h4 id="named-flows-layout">Step 3: named flows layout</h4>
         <a href="#processing-model">rules</a> 
         described earlier in this document.</p>
 
+    <div class="note">
+        <p>The model for resolving auto sized regions will cause, under certain circumstances,
+            the flow content to be overset or underset. In other words, it will not fit tightly.
+            The model prevents having circular dependencies in the layout model. Implementations
+            may decide to apply further layout steps to ensure that the whole flow content is 
+            displayed to the user, even in edge cases.</p>
+    </div>
+        
     <h3 id="regions-visual-formatting-implementation-note">Regions visual formatting: implementation note</h3>
 
     <p>The process for resolving an RFCB's 'height' and the three-step process used to