[html5] r3751 - [ac] (0) Extend <footer> to be more like <header>.

[whatwg at whatwg.org]

Author: ianh
Date: 2009-09-04 02:12:55 -0700 (Fri, 04 Sep 2009)
New Revision: 3751

Modified:
   index
   source
Log:
[ac] (0) Extend <footer> to be more like <header>.

Modified: index
===================================================================
--- index	2009-09-04 07:47:38 UTC (rev 3750)
+++ index	2009-09-04 09:12:55 UTC (rev 3751)
@@ -13081,10 +13081,8 @@
    <dt>Contexts in which this element may be used:</dt>
    <dd>Where <a href=#flow-content>flow content</a> is expected.</dd>
    <dt>Content model:</dt>
-   <dd><a href=#flow-content>Flow content</a>, but with no <a href=#heading-content>heading
-   content</a> descendants, no <a href=#sectioning-content>sectioning content</a>
-   descendants, and no <code><a href=#the-header-element>header</a></code> or <code><a href=#the-footer-element>footer</a></code>
-   element descendants.</dd>
+   <dd><a href=#flow-content>Flow content</a>, but with no <code><a href=#the-header-element>header</a></code> or
+   <code><a href=#the-footer-element>footer</a></code> element descendants.</dd>
    <dt>Content attributes:</dt>
    <dd><a href=#global-attributes>Global attributes</a></dd>
    <dt>DOM interface:</dt>
@@ -13101,12 +13099,15 @@
   <p>Footers don't necessarily have to appear at the end of a section,
   though they usually do.</p>
 
-  <p>The <code><a href=#the-footer-element>footer</a></code> element is inappropriate for containing
-  entire sections. For appendices, indexes, long colophons, verbose
-  license agreements, and other such content which needs sectioning
-  with headings and so forth, regular <code><a href=#the-section-element>section</a></code> elements
-  should be used, not a <code><a href=#the-footer-element>footer</a></code>.</p>
+  <p>When the <code><a href=#the-footer-element>footer</a></code> element contains entire sections,
+  they <a href=#represents title=represents>represent</a> appendices, indexes,
+  long colophons, verbose license agreements, and other such
+  content.</p>
 
+  <p class=note>The <code><a href=#the-footer-element>footer</a></code> element is not
+  <a href=#sectioning-content>sectioning content</a>; it doesn't introduce a new
+  section.</p>
+
   <div class=example>
 
    <p>Here is a page with two footers, one at the top and one at the

Modified: source
===================================================================
--- source	2009-09-04 07:47:38 UTC (rev 3750)
+++ source	2009-09-04 09:12:55 UTC (rev 3751)
@@ -13970,10 +13970,8 @@
    <dt>Contexts in which this element may be used:</dt>
    <dd>Where <span>flow content</span> is expected.</dd>
    <dt>Content model:</dt>
-   <dd><span>Flow content</span>, but with no <span>heading
-   content</span> descendants, no <span>sectioning content</span>
-   descendants, and no <code>header</code> or <code>footer</code>
-   element descendants.</dd>
+   <dd><span>Flow content</span>, but with no <code>header</code> or
+   <code>footer</code> element descendants.</dd>
    <dt>Content attributes:</dt>
    <dd><span>Global attributes</span></dd>
    <dt>DOM interface:</dt>
@@ -13992,12 +13990,15 @@
   <p>Footers don't necessarily have to appear at the end of a section,
   though they usually do.</p>
 
-  <p>The <code>footer</code> element is inappropriate for containing
-  entire sections. For appendices, indexes, long colophons, verbose
-  license agreements, and other such content which needs sectioning
-  with headings and so forth, regular <code>section</code> elements
-  should be used, not a <code>footer</code>.</p>
+  <p>When the <code>footer</code> element contains entire sections,
+  they <span title="represents">represent</span> appendices, indexes,
+  long colophons, verbose license agreements, and other such
+  content.</p>
 
+  <p class="note">The <code>footer</code> element is not
+  <span>sectioning content</span>; it doesn't introduce a new
+  section.</p>
+
   <div class="example">
 
    <p>Here is a page with two footers, one at the top and one at the