Browse files

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

git-svn-id: http://svn.whatwg.org/webapps@3751 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
1 parent 3ed5ad4 commit ea6c2509e1fa20698a861a10ac83430fe114529a @Hixie Hixie committed Sep 4, 2009
Showing with 20 additions and 18 deletions.
  1. +10 −9 index
  2. +10 −9 source
View
19 index
@@ -13081,10 +13081,8 @@ isn't his only passion. He also enjoys other pleasures.&lt;/p&gt;
<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,11 +13099,14 @@ isn't his only passion. He also enjoys other pleasures.&lt;/p&gt;
<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>
View
19 source
@@ -13970,10 +13970,8 @@ isn't his only passion. He also enjoys other pleasures.&lt;/p>
<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,11 +13990,14 @@ isn't his only passion. He also enjoys other pleasures.&lt;/p>
<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">

0 comments on commit ea6c250

Please sign in to comment.