[css-regions] more clarifications on fragment rendering in note 10

Author: astearns

css-regions/Overview.html

@@ -12,7 +12,7 @@
    rel=dcterms.rights>
   <meta content="CSS Regions Module Level 3" name=dcterms.title>
   <meta content=text name=dcterms.type>
-  <meta content=2013-04-16 name=dcterms.date>
+  <meta content=2013-04-17 name=dcterms.date>
   <meta content="Vincent Hardy" name=dcterms.creator>
   <meta content="Rossen Atanassov" name=dcterms.creator>
   <meta content="Alan Stearns" name=dcterms.creator>
@@ -50,7 +50,7 @@
 
    <h1 id=css-regions-module>CSS Regions Module Level 3</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 16 April 2013</h2>
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 17 April 2013</h2>
 
    <dl>
     <dt>This version:
@@ -984,17 +984,6 @@ <h3 id=the-flow-from-property><span class=secno>3.2. </span>The ‘<a
     does not result in a CSS Region.
   </div>
 
-  <div class="issue-marker wrapper">
-   <div class=issue-marker data-bug_id=15827 data-bug_status=NEW> <a
-    href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15824">Issue-15827</a>
-
-    <div class=issue-details>
-     <p class=short-desc>Specify behavior of stacking contexts that are split
-      between regions
-    </div>
-   </div>
-  </div>
-
   <p><a href="#css-region" title=region>CSS Regions</a> create a new <a
    href="http://www.w3.org/TR/CSS2/visuren.html#z-index">stacking
    context</a>. <a href="#css-region" title=region>CSS Regions</a> establish
@@ -1015,6 +1004,12 @@ <h3 id=the-flow-from-property><span class=secno>3.2. </span>The ‘<a
     new stacking context, it is clear that each fragment is rendered
     separately and their rendering order follows the regular CSS rendering
     model.
+
+   <p>Fragments rendering separately is also relevant to elements that might
+    normally be rendered as a unit (for example, an element with its own
+    stacking context, or with transparency). Each fragment of these elements
+    is separately contained in the stacking context created by the <span>CSS
+    Region</span>, so each fragment of these elements is rendered separately.
   </div>
 
   <p>See the <a href="#regions-visual-formatting-details">regions visual

css-regions/Overview.src.html

@@ -809,18 +809,6 @@ <h3 id="the-flow-from-property">The 'flow-from' property</h3>
         So 'flow-from' combined with those display values 
         does not result in a CSS Region.</p>
     </div>
-    
-    <div class="issue-marker wrapper">
-     <div class="issue-marker" data-bug_id="15827" data-bug_status="NEW">
-        
-        <a href=
-        "https://www.w3.org/Bugs/Public/show_bug.cgi?id=15824">Issue-15827</a>
-
-        <div class="issue-details">
-            <p class="short-desc">Specify behavior of stacking contexts that are split between regions</p>
-        </div>    
-     </div>
-    </div>
 
     <p><span title="region">CSS Regions</span> 
       create a new 
@@ -849,6 +837,17 @@ <h3 id="the-flow-from-property">The 'flow-from' property</h3>
           it is clear that each fragment is rendered separately 
           and their rendering order follows 
           the regular CSS rendering model.</p>
+        <p>Fragments rendering separately 
+          is also relevant to elements that might normally 
+          be rendered as a unit 
+          (for example, 
+          an element with its own stacking context, 
+          or with transparency). 
+          Each fragment of these elements 
+          is separately contained in the stacking context 
+          created by the <span>CSS Region</span>, 
+          so each fragment of these elements 
+          is rendered separately.</p>
     </div>
 
     <p>See the