Short URL: http://html5.org/r/3751
| SVN | Bug | Comment | Time (UTC) |
|---|---|---|---|
| 3751 | 2009-09-04 09:12 |
Index: source
===================================================================
--- source (revision 3750)
+++ source (revision 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