Fixed issue styling to hide older resoved issues. Added note about how a region with no flow content is still a region

vhardy · vhardy · commit 494255d842e0 · 2011-10-29T00:21:29.000Z
diff --git a/css3-regions/Overview.html b/css3-regions/Overview.html
@@ -44,6 +44,10 @@
          div.issue-marker a {
              color: red;
          }
+         
+         .issue.resolved, .issue.stale, .issue.moved {
+             display: none;
+         }
        </style>
 
  <body>
@@ -53,14 +57,14 @@
 
    <h1 id=css-regions-module>CSS Regions Module</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 27 October
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 29 October
     2011</h2>
 
    <dl>
     <dt>This version:
 
     <dd><a
-     href="http://www.w3.org/TR/2011/ED-css3-regions-20111027/">http://www.w3.org/csswg/css3-regions</a>
+     href="http://www.w3.org/TR/2011/ED-css3-regions-20111029/">http://www.w3.org/csswg/css3-regions</a>
 
     <dt>Latest version:
 
@@ -780,8 +784,36 @@ <h3 id=the-flow-from-property><span class=secno>4.2. </span>The &lsquo;<a
     then the element does not format any content visually.
   </dl>
 
-  <p>Note that a region's document children are not visually formatted unless
-   they are directed to a named flow referenced by one or more regions.
+  <p class=note>A region's document children are not visually formatted
+   unless they are directed to a named flow referenced by one or more
+   regions.
+
+  <div class=note>
+   <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>
+   <code></code>
+   <pre>
+&lt;style&gt;
+  .article{
+    flow-into: thread;
+  }
+  .region{
+    flow-from: thread;
+  }
+&lt;/style&gt;
+&lt;html&gt;
+  &lt;body&gt;
+    &lt;div class=region&gt;div content&lt;/div&gt;
+  &lt;/body&gt;
+&lt;/html&gt;
+        </pre>
+   There is no element matching the <code>.article</code> selector and
+   therefore no content in the <code>thread</code> flow. However, the element
+   matching the <code>.region</code> selector is still associated with that
+   empty named flow and, consequently, its children are not formatted
+   visually.</div>
 
   <div class="issue resolved">
    <p><a
diff --git a/css3-regions/Overview.src.html b/css3-regions/Overview.src.html
@@ -44,6 +44,10 @@
          div.issue-marker a {
              color: red;
          }
+         
+         .issue.resolved, .issue.stale, .issue.moved {
+             display: none;
+         }
        </style>
 
 
@@ -594,9 +598,33 @@ <h3 id="the-flow-from-property">The 'flow-from' property</h3>
         </dd>
     </dl>
 
-    <p>Note that a region's document children are not visually formatted unless they are directed to a named flow
+    <p class="note">A region's document children are not visually formatted unless they are directed to a named flow
         referenced by one or more regions.</p>
         
+    <div class="note"><p>An element becomes a region when its '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>
+        <code><pre>
+&lt;style&gt;
+  .article{
+    flow-into: thread;
+  }
+  .region{
+    flow-from: thread;
+  }
+&lt;/style&gt;
+&lt;html&gt;
+  &lt;body&gt;
+    &lt;div class=region&gt;div content&lt;/div&gt;
+  &lt;/body&gt;
+&lt;/html&gt;
+        </code></pre>
+        
+        There is no element matching the <code>.article</code> selector and therefore no 
+        content in the <code>thread</code> flow. However, the element matching the <code>.region</code>
+        selector is still associated with that empty named flow and, consequently, its children
+        are not formatted visually.
+        </div>
     <div class="issue resolved">
         <p><a href="http://lists.w3.org/Archives/Public/www-style/2011Aug/0069.html">Third resolution on
             Regions at the Seattle Face to Face meeting, July 2011</a>. Superseded by resolution during 
