Mercurial > drafts / changeset

     1.1 --- a/css-regions/Overview.html	Wed Apr 17 11:34:59 2013 +0200
     1.2 +++ b/css-regions/Overview.html	Wed Apr 17 07:50:15 2013 -0700
     1.3 @@ -12,7 +12,7 @@
     1.4     rel=dcterms.rights>
     1.5    <meta content="CSS Regions Module Level 3" name=dcterms.title>
     1.6    <meta content=text name=dcterms.type>
     1.7 -  <meta content=2013-04-16 name=dcterms.date>
     1.8 +  <meta content=2013-04-17 name=dcterms.date>
     1.9    <meta content="Vincent Hardy" name=dcterms.creator>
    1.10    <meta content="Rossen Atanassov" name=dcterms.creator>
    1.11    <meta content="Alan Stearns" name=dcterms.creator>
    1.12 @@ -50,7 +50,7 @@
    1.13  
    1.14     <h1 id=css-regions-module>CSS Regions Module Level 3</h1>
    1.15  
    1.16 -   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 16 April 2013</h2>
    1.17 +   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 17 April 2013</h2>
    1.18  
    1.19     <dl>
    1.20      <dt>This version:
    1.21 @@ -984,17 +984,6 @@
    1.22      does not result in a CSS Region.
    1.23    </div>
    1.24  
    1.25 -  <div class="issue-marker wrapper">
    1.26 -   <div class=issue-marker data-bug_id=15827 data-bug_status=NEW> <a
    1.27 -    href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15824">Issue-15827</a>
    1.28 -
    1.29 -    <div class=issue-details>
    1.30 -     <p class=short-desc>Specify behavior of stacking contexts that are split
    1.31 -      between regions
    1.32 -    </div>
    1.33 -   </div>
    1.34 -  </div>
    1.35 -
    1.36    <p><a href="#css-region" title=region>CSS Regions</a> create a new <a
    1.37     href="http://www.w3.org/TR/CSS2/visuren.html#z-index">stacking
    1.38     context</a>. <a href="#css-region" title=region>CSS Regions</a> establish
    1.39 @@ -1015,6 +1004,12 @@
    1.40      new stacking context, it is clear that each fragment is rendered
    1.41      separately and their rendering order follows the regular CSS rendering
    1.42      model.
    1.43 +
    1.44 +   <p>Fragments rendering separately is also relevant to elements that might
    1.45 +    normally be rendered as a unit (for example, an element with its own
    1.46 +    stacking context, or with transparency). Each fragment of these elements
    1.47 +    is separately contained in the stacking context created by the <span>CSS
    1.48 +    Region</span>, so each fragment of these elements is rendered separately.
    1.49    </div>
    1.50  
    1.51    <p>See the <a href="#regions-visual-formatting-details">regions visual

     2.1 --- a/css-regions/Overview.src.html	Wed Apr 17 11:34:59 2013 +0200
     2.2 +++ b/css-regions/Overview.src.html	Wed Apr 17 07:50:15 2013 -0700
     2.3 @@ -809,18 +809,6 @@
     2.4          So 'flow-from' combined with those display values 
     2.5          does not result in a CSS Region.</p>
     2.6      </div>
     2.7 -    
     2.8 -    <div class="issue-marker wrapper">
     2.9 -     <div class="issue-marker" data-bug_id="15827" data-bug_status="NEW">
    2.10 -        
    2.11 -        <a href=
    2.12 -        "https://www.w3.org/Bugs/Public/show_bug.cgi?id=15824">Issue-15827</a>
    2.13 -
    2.14 -        <div class="issue-details">
    2.15 -            <p class="short-desc">Specify behavior of stacking contexts that are split between regions</p>
    2.16 -        </div>    
    2.17 -     </div>
    2.18 -    </div>
    2.19  
    2.20      <p><span title="region">CSS Regions</span> 
    2.21        create a new 
    2.22 @@ -849,6 +837,17 @@
    2.23            it is clear that each fragment is rendered separately 
    2.24            and their rendering order follows 
    2.25            the regular CSS rendering model.</p>
    2.26 +        <p>Fragments rendering separately 
    2.27 +          is also relevant to elements that might normally 
    2.28 +          be rendered as a unit 
    2.29 +          (for example, 
    2.30 +          an element with its own stacking context, 
    2.31 +          or with transparency). 
    2.32 +          Each fragment of these elements 
    2.33 +          is separately contained in the stacking context 
    2.34 +          created by the <span>CSS Region</span>, 
    2.35 +          so each fragment of these elements 
    2.36 +          is rendered separately.</p>
    2.37      </div>
    2.38  
    2.39      <p>See the