[css-regions] named flow structure clarifications for issue 16002

Tue, 02 Oct 2012 14:16:43 -0700

author
Alan Stearns <stearns@adobe.com>
date
Tue, 02 Oct 2012 14:16:43 -0700
changeset 6812
b76903becabe
parent 6811
65639933e3e6
child 6813
4bad02174b9e

[css-regions] named flow structure clarifications for issue 16002

css3-regions/Overview.html file | annotate | diff | comparison | revisions
css3-regions/Overview.src.html file | annotate | diff | comparison | revisions
     1.1 --- a/css3-regions/Overview.html	Tue Oct 02 09:28:31 2012 -0700
     1.2 +++ b/css3-regions/Overview.html	Tue Oct 02 14:16:43 2012 -0700
     1.3 @@ -646,14 +646,6 @@
     1.4      </div>
     1.5     </div>
     1.6  
     1.7 -   <div class=issue-marker data-bug_id=16002 data-bug_status=NEW> <a
     1.8 -    href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16002">Issue-16002</a>
     1.9 -
    1.10 -    <div class=issue-details>
    1.11 -     <p class=short-desc>flow-into and anonymous blocks or fix-ups
    1.12 -    </div>
    1.13 -   </div>
    1.14 -
    1.15     <div class=issue-marker data-bug_id=16527 data-bug_status=ASSIGNED> <a
    1.16      href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16527">Issue-16527</a>
    1.17  
    1.18 @@ -779,7 +771,10 @@
    1.19     ignored.
    1.20  
    1.21    <p>Elements in a <a href="#named-flow0">named flow</a> are sequenced in
    1.22 -   document order.
    1.23 +   document order. The structure of a named flow is equivalent to the result
    1.24 +   of moving the elements to a common parent. The visual formatting model
    1.25 +   uses the relationships between elements in the named flow structure as
    1.26 +   input, rather than the elements’ original positions.
    1.27  
    1.28    <div class=note><span class=note-prefix>Note </span>
    1.29     <p>The ‘<a href="#flow-into"><code
     2.1 --- a/css3-regions/Overview.src.html	Tue Oct 02 09:28:31 2012 -0700
     2.2 +++ b/css3-regions/Overview.src.html	Tue Oct 02 14:16:43 2012 -0700
     2.3 @@ -426,12 +426,6 @@
     2.4              <p class="short-desc">Creating a named flow from external resource</p>
     2.5          </div>
     2.6      </div>
     2.7 -    <div class="issue-marker" data-bug_id="16002" data-bug_status="NEW">
     2.8 -        <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16002">Issue-16002</a>
     2.9 -        <div class="issue-details">
    2.10 -            <p class="short-desc">flow-into and anonymous blocks or fix-ups</p>
    2.11 -        </div>  
    2.12 -    </div>
    2.13      <div class="issue-marker" data-bug_id="16527" data-bug_status="ASSIGNED">
    2.14      <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16527">Issue-16527</a>
    2.15      <div class="issue-details">
    2.16 @@ -574,7 +568,15 @@
    2.17        on subsequent regions is ignored.</p>
    2.18  
    2.19      <p>Elements in a <span>named flow</span> 
    2.20 -      are sequenced in document order.</p>
    2.21 +      are sequenced in document order. 
    2.22 +      The structure of a named flow 
    2.23 +      is equivalent to the result 
    2.24 +      of moving the elements to a common parent. 
    2.25 +      The visual formatting model 
    2.26 +      uses the relationships between elements 
    2.27 +      in the named flow structure as input, 
    2.28 +      rather than the elements&rsquo; original positions.
    2.29 +    </p>
    2.30  
    2.31      <div class="note"><span class="note-prefix">Note </span>
    2.32          <p>The 'flow-into' property moves an element into the flow 

mercurial