[html5] r4053 - [e] (0) Add an ID. (also, add a missing word) Fixing http://www.w3.org/Bugs/Publ [...]
whatwg at whatwg.org
whatwg at whatwg.org
Tue Sep 29 04:11:45 PDT 2009
Author: ianh
Date: 2009-09-29 04:11:44 -0700 (Tue, 29 Sep 2009)
New Revision: 4053
Modified:
index
source
Log:
[e] (0) Add an ID. (also, add a missing word)
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=7739
Modified: index
===================================================================
--- index 2009-09-29 11:01:15 UTC (rev 4052)
+++ index 2009-09-29 11:11:44 UTC (rev 4053)
@@ -12997,13 +12997,13 @@
element when it would make sense to syndicate the contents of the
element.</p>
- <p class=note>The <code><a href=#the-section-element>section</a></code> element is not a generic
- container element. When an element is needed for styling purposes or
- as a convenience for scripting, authors are encouraged to use the
- <code><a href=#the-div-element>div</a></code> element instead. A general rule is that the
- <code><a href=#the-section-element>section</a></code> element is appropriate only if the element's
- contents would be listed explicitly in the document's
- <a href=#outline>outline</a>.</p>
+ <p class=note id=use-div-for-wrappers>The <code><a href=#the-section-element>section</a></code>
+ element is not a generic container element. When an element is
+ needed for styling purposes or as a convenience for scripting,
+ authors are encouraged to use the <code><a href=#the-div-element>div</a></code> element
+ instead. A general rule is that the <code><a href=#the-section-element>section</a></code> element is
+ appropriate only if the element's contents would be listed
+ explicitly in the document's <a href=#outline>outline</a>.</p>
<div class=example>
@@ -64985,8 +64985,8 @@
attribute names, attribute values, text nodes, etc. While
implementors are encouraged to avoid arbitrary limits, it is
recognized that <a href=#hardwareLimitations>practical
- concerns</a> will likely force user agents to impose nesting
- depths.</p>
+ concerns</a> will likely force user agents to impose nesting depth
+ constraints.</p>
<h5 id=creating-and-inserting-elements><span class=secno>9.2.5.1 </span>Creating and inserting elements</h5>
Modified: source
===================================================================
--- source 2009-09-29 11:01:15 UTC (rev 4052)
+++ source 2009-09-29 11:11:44 UTC (rev 4053)
@@ -13834,13 +13834,13 @@
element when it would make sense to syndicate the contents of the
element.</p>
- <p class="note">The <code>section</code> element is not a generic
- container element. When an element is needed for styling purposes or
- as a convenience for scripting, authors are encouraged to use the
- <code>div</code> element instead. A general rule is that the
- <code>section</code> element is appropriate only if the element's
- contents would be listed explicitly in the document's
- <span>outline</span>.</p>
+ <p class="note" id="use-div-for-wrappers">The <code>section</code>
+ element is not a generic container element. When an element is
+ needed for styling purposes or as a convenience for scripting,
+ authors are encouraged to use the <code>div</code> element
+ instead. A general rule is that the <code>section</code> element is
+ appropriate only if the element's contents would be listed
+ explicitly in the document's <span>outline</span>.</p>
<div class="example">
@@ -80078,8 +80078,8 @@
attribute names, attribute values, text nodes, etc. While
implementors are encouraged to avoid arbitrary limits, it is
recognized that <a href="#hardwareLimitations">practical
- concerns</a> will likely force user agents to impose nesting
- depths.</p>
+ concerns</a> will likely force user agents to impose nesting depth
+ constraints.</p>
<h5>Creating and inserting elements</h5>
More information about the Commit-Watchers
mailing list