editorial changes to section 3

Author: astearns

css3-regions/Overview.html

@@ -255,7 +255,7 @@ <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 11 April 2012</h2>
     <dt>Issues List:
 
     <dd><a
-     href="https://www.w3.org/Bugs/Public/buglist.cgi?product=CSS&component=CSS%20Regions&resolution=---">Bugzilla
+     href="https://www.w3.org/Bugs/Public/buglist.cgi?product=CSS&component=Regions&resolution=---">Bugzilla
      Bugs for CSS regions</a>
 
     <dt>Discussion:
@@ -531,13 +531,6 @@ <h2 id=introduction><span class=secno>1. </span>Introduction</h2>
 
   <p><em>This section is non-normative.</em>
 
-  <div class=issue-marker data-bug_id=15159 data-bug_status=NEW> <a
-   href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15159">Bug-15159</a>
-   <div class=issue-details>
-    <p class=short-desc>Add code samples to the CSS regions use cases page</p>
-   </div>
-  </div>
-
   <p>Displaying the complex layouts of a typical magazine, newspaper, or
    textbook on the web requires capabilities beyond those available in
    existing CSS modules. Dynamic magazine layout in particular requires
@@ -573,13 +566,6 @@ <h3 id=named-flows-and-regions><span class=secno>1.1. </span>Named flows
    <p class=caption>Layout requiring sophisticated content flow</p>
   </div>
 
-  <div class=issue-marker data-bug_id=15131 data-bug_status=NEW> <a
-   href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15131">Bug-15131</a>
-   <div class=issue-details>
-    <p class=short-desc>Add layout to initial example</p>
-   </div>
-  </div>
-
   <p>The designer's intent is to position an image in box &lsquo;<code
    class=property>A</code>&rsquo; and to flow an article's content from box
    &lsquo;<code class=css>1</code>&rsquo; through boxes &lsquo;<code
@@ -825,7 +811,7 @@ <h3 id=the-flow-into-property><span class=secno>3.1. </span>The &lsquo;<a
 
   <p>The ‘flow-into’ property can place an element into a <a
    href="#named-flow0">named flow</a>. Elements that belong to the same flow
-   are laid out in the regions associated with that flow.
+   are laid out in the region chain associated with that flow.
 
   <table class=propdef summary="flow property definition">
    <tbody>
@@ -896,27 +882,28 @@ <h3 id=the-flow-into-property><span class=secno>3.1. </span>The &lsquo;<a
     class=property>initial</code>&rsquo; are invalid flow names.
   </dl>
 
-  <p>A <a href="#named-flow0">named flow</a> needs to be associated with one
-   or more regions for its elements to be visually formatted. If no region is
-   associated with a given <a href="#named-flow0">named flow</a>, the
-   elements in the <a href="#named-flow0">named flow</a> are not rendered:
-   they do not generate boxes and are not displayed.
+  <p>A <a href="#named-flow0">named flow</a> needs to be associated with a
+   region chain (one or more CSS regions) for its elements to be visually
+   formatted. If no region chain is associated with a given <a
+   href="#named-flow0">named flow</a>, the elements in the <a
+   href="#named-flow0">named flow</a> are not rendered: they do not generate
+   boxes and are not displayed.
 
   <p>The children of an element with a specified flow may themselves have a
    specified flow.
 
   <p>If an element has the same specified flow as one of its ancestors, it
-   becomes a sibling of it's ancestor for the purpose of layout in the
-   regions laying out content from that flow.
+   becomes a sibling of its ancestor for the purpose of layout in the region
+   chain laying out content from that flow.
 
   <p>The &lsquo;<a href="#flow-into"><code
    class=property>flow-into</code></a>&rsquo; property does not affect the
    CSS cascade and inheritance for the elements on which it is specified. The
    &lsquo;<a href="#flow-into"><code
    class=property>flow-into</code></a>&rsquo; property affects the visual
    formatting of elements placed into a <a href="#named-flow0">named flow</a>
-   and of regions laying out content from a <a href="#named-flow0">named
-   flow</a>.
+   and of the region chain laying out content from a <a
+   href="#named-flow0">named flow</a>.
 
   <div class="issue-marker wrapper">
    <div class=issue-marker data-bug_id=15858 data-bug_status=NEW> <a
@@ -985,7 +972,7 @@ <h3 id=the-flow-into-property><span class=secno>3.1. </span>The &lsquo;<a
     probably not intentional). This will make all the descendants of table
     elements siblings in the <a href="#named-flow0">named flow</a>. Having
     the descendants become siblings in the <a href="#named-flow0">named
-    flow</a> results in a different processing (see the <a
+    flow</a> results in a different processing (see <a
     href="http://www.w3.org/TR/2011/REC-CSS2-20110607/tables.html#anonymous-boxes">CSS
     2.1&lsquo;<code class=css>s anonymous table objects</code></a>). This
     note illustrates how authors must exercise caution when choosing a
@@ -1065,31 +1052,32 @@ <h3 id=the-flow-from-property><span class=secno>3.2. </span>The &lsquo;<a
    <dd> If the &lsquo;<code class=property>content</code>&rsquo; property
     computes to something else than &lsquo;<code
     class=property>normal</code>&rsquo;, the element does not become a
-    region. If the &lsquo;<code class=property>content</code>&rsquo; property
-    computes to &lsquo;<code class=property>normal</code>&rsquo;, then the
-    element becomes a <span>region</span> and is ordered in a <span>region
-    chain</span> according to its document order. The content from the flow
-    with the <a
+    <span>CSS Region</span>. If the &lsquo;<code
+    class=property>content</code>&rsquo; property computes to &lsquo;<code
+    class=property>normal</code>&rsquo;, then the element becomes a <span>CSS
+    Region</span> and is ordered in a <span>region chain</span> according to
+    its document order. The content from the flow with the <a
     href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a>
     name will be <a href="#region-flow-break">broken into fragments</a> and
     visually formatted in the <a
     href="http://www.w3.org/TR/CSS21/visuren.html#principal-box">principal
-    boxes</a> of the regions in the region chain. If there is no flow with
-    name &lt;ident&gt;, then the element does not format any content
-    visually. <br>
+    boxes</a> of the <span>regions</span> in the <span>region chain</span>.
+    <br>
+    If there is no flow with name &lt;ident&gt;, then the element does not
+    format any content visually. <br>
     Likewise, if the element is part of the flow with name &lt;ident&gt;,
     then the element does not format any content visually.
   </dl>
 
-  <p class=note><span class=note-prefix>Note </span>A region's document
-   children are not visually formatted unless they are directed to a <a
-   href="#named-flow0">named flow</a> referenced by one or more regions.
+  <p>A <span>CSS Region</span>&lsquo;<code class=css>s document children are
+   not visually formatted unless they are directed to a <a
+   href="#named-flow0">named flow</a> with an associated <span>region
+   chain</span>.</code>
 
   <div class=note><span class=note-prefix>Note </span>
-   <p>An element becomes a region when its &lsquo;<a href="#flow-from"><code
-    class=property>flow-from</code></a>&rsquo; property is set to a valid
-    &lt;ident&gt; value, even if there is no content contributing to the
-    referenced flow. For example:</p>
+   <p>An element becomes a <span>CSS Region</span> when its &rsquo;flow-from'
+    property is set to a valid &lt;ident&gt; value, even if there is no
+    content contributing to the referenced flow. For example:</p>
 
    <pre>
 &lt;style&gt;
@@ -1139,33 +1127,33 @@ <h3 id=the-flow-from-property><span class=secno>3.2. </span>The &lsquo;<a
    </div>
   </div>
 
-  <p><span title=region>Regions</span> create a new <a
+  <p><span title=region>CSS Regions</span> create a new <a
    href="http://www.w3.org/TR/CSS2/visuren.html#z-index">stacking
-   context</a>. <span title=region>Regions</span> establish a new <a
+   context</a>. <span title=region>CSS Regions</span> establish a new <a
    href="http://www.w3.org/TR/CSS2/visuren.html#block-formatting">block
    formatting Context</a>.
 
   <div class=note><span class=note-prefix>Note </span>
-   <p>With regions, an element may be split across multiple regions and these
-    regions may overlap (for example if they are absolutely positioned). So
-    fragments of the same element can overlap each other. Since each element
-    has a single z-index, it would be required to find another mechanism to
-    decide in which order the  fragments are rendered. Since each region
-    creates a new stacking context, it is clear that each region is rendered
-    separately and their rendering order follows the regular CSS rendering
-    model.</p>
+   <p>With <span>region chains</span>, an element may be split across
+    multiple boxes and these boxes may overlap (for example if they are
+    absolutely positioned). So fragments of the same element can overlap each
+    other. Since each element has a single z-index, it would be required to
+    find another mechanism to decide in which order the fragments are
+    rendered. Since each <span>CSS Region</span> creates a new stacking
+    context, it is clear that each fragment is rendered separately and their
+    rendering order follows the regular CSS rendering model.</p>
   </div>
 
   <p>Floats or other exclusions (see <a href="#CSS3-EXCLUSIONS"
    rel=biblioentry>[CSS3-EXCLUSIONS]<!--{{CSS3-EXCLUSIONS}}--></a>)
-   potentially impact the content laid out in regions, just as for
+   potentially impact the content laid out in region chains, just as for
    non-regions.
 
   <p>See the <a href="#regions-visual-formatting-details">regions visual
    formatting details</a> section for a description of how &lsquo;<code
    class=property>width</code>&rsquo; and &lsquo;<code
-   class=property>height</code>&rsquo; values are resolved for
-   <span>region</span> boxes.
+   class=property>height</code>&rsquo; values are resolved for <span>CSS
+   Region</span> boxes.
 
   <h3 id=region-flow-break><span class=secno>3.3. </span>Region flow break
    properties: &lsquo;<a href="#break-before"><code
@@ -1227,7 +1215,7 @@ <h3 id=region-flow-break><span class=secno>3.3. </span>Region flow break
     <tr>
      <td><em>Media:</em>
 
-     <td>paged
+     <td>visual
 
     <tr>
      <td><em>Computed&nbsp;value:</em>
@@ -1271,7 +1259,7 @@ <h3 id=region-flow-break><span class=secno>3.3. </span>Region flow break
     <tr>
      <td><em>Media:</em>
 
-     <td>paged
+     <td>visual
 
     <tr>
      <td><em>Computed&nbsp;value:</em>
@@ -1314,7 +1302,7 @@ <h3 id=region-flow-break><span class=secno>3.3. </span>Region flow break
     <tr>
      <td><em>Media:</em>
 
-     <td>paged
+     <td>visual
 
     <tr>
      <td><em>Computed&nbsp;value:</em>
@@ -1388,7 +1376,7 @@ <h3 id=the-region-overflow-property><span class=secno>3.4. </span>The
     <tr>
      <td><em>Media:</em>
 
-     <td>paged
+     <td>visual
 
     <tr>
      <td><em>Computed&nbsp;value:</em>
@@ -1572,6 +1560,9 @@ <h3 id=the-at-region-style-rule><span class=secno>3.5. </span>The @region
 
    <li><a href="http://www.w3.org/TR/CSS2/colors.html">color property</a>
 
+   <li><a href="http://www.w3.org/TR/css3-color/#transparency">opacity
+    property</a>
+
    <li><a href="http://www.w3.org/TR/css3-background/#backgrounds">background
     property</a>
 
@@ -1900,13 +1891,6 @@ <h2 id="cssom_view_and_css_regions"><span class=secno>6. </span>CSSOM view
    additional space required to fit the larger text or some regions may need
    to be removed for smaller text.
 
-  <div class=issue-marker data-bug_id=15010 data-bug_status=NEW> <a
-   href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15010">Bug-15010</a>
-   <div class=issue-details>
-    <p class=short-desc>Need to add a CSSRegionRule to Region OM</p>
-   </div>
-  </div>
-
   <h3 id=the-namedflow-interface><span class=secno>6.1. </span>The NamedFlow
    interface</h3>
 
@@ -1928,14 +1912,6 @@ <h3 id=the-namedflow-interface><span class=secno>6.1. </span>The NamedFlow
     transitions</p>
   </div>
 
-  <div class=issue-marker data-bug_id=14948 data-bug_status=NEW> <a
-   href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=14948">Bug-14948</a>
-   <div class=issue-details>
-    <p class=short-desc>What should getFlowByName return if there is no flow
-     with the given name?</p>
-   </div>
-  </div>
-
   <p>An addition method and attribute on the <a
    href="http://www.w3.org/TR/dom/#interface-document"><code
    class=idl>Document</code></a> interface provide access to <a
@@ -2000,16 +1976,6 @@ <h3 id=the-namedflow-interface><span class=secno>6.1. </span>The NamedFlow
     no matter what the state of the <a href="#named-flow0">named flow</a> is.
   </ul>
 
-  <div class=issue-marker data-bug_id=15828 data-bug_status=NEW> <a
-   href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15828">Bug-15828</a>
-   <div class=issue-details>
-    <p class=short-desc>Should add a &lsquo;<a
-     href="#dom-named-flow-name"><code class=property>name</code></a>&rsquo;
-     property on NamedFlow and should have a Document method to get all
-     existing NamedFlow instances.</p>
-   </div>
-  </div>
-
   <p>The <dfn id=dom-named-flow-collection><code
    class=idl>NamedFlowCollection</code></dfn> interface provides a list of
    current <a href="#dom-named-flow"><code class=idl>NamedFlow</code></a>
@@ -2046,14 +2012,6 @@ <h3 id=the-namedflow-interface><span class=secno>6.1. </span>The NamedFlow
    that <a href="#named-flow0">named flow</a> has transitioned to the
    <code>REFERENCED</code> or the <code>STALE</code> states.
 
-  <div class=issue-marker data-bug_id=15879 data-bug_status=NEW> <a
-   href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15879">Bug-15879</a>
-   <div class=issue-details>
-    <p class=short-desc>getRegionsByContentNode and contentNodes: change
-     naming?</p>
-   </div>
-  </div>
-
   <pre class=idl>
 interface <a
    href="#dom-named-flow">NamedFlow</a> implements <a
@@ -2249,13 +2207,6 @@ <h3 id=the-region-interface><span class=secno>6.2. </span>The Region
   <h3 id=region-flow-layout-events><span class=secno>6.3. </span>Region flow
    layout events</h3>
 
-  <div class=issue-marker data-bug_id=15009 data-bug_status=NEW> <a
-   href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15009">Bug-15009</a>
-   <div class=issue-details>
-    <p class=short-desc>Should we have additional events for CSS Regions?</p>
-   </div>
-  </div>
-
   <p><a href="#dom-named-flow"><code class=idl>NamedFlow</code></a> objects
    are <a href="">Event Targets</a> which dispatch <code
    class=idl>regionLayoutUpdate</code> events when there is a possible layout
@@ -2956,6 +2907,11 @@ <h3 id="changes_from_June_09_2011"><span class=secno>12.1. </span>Changes
     auto sizing on regions.
 
    <li>Reworked the initial specification example.
+
+   <li>Changed break and region-overflow properties to apply to visual media
+    instead of paged.
+
+   <li>Added opacity to region styling.
   </ul>
 
   <h3 id="changes_from_June_09_2011"><span class=secno>12.2. </span>Changes