[html5] r1251 - /
whatwg at whatwg.org
whatwg at whatwg.org
Tue Feb 26 01:38:00 PST 2008
Author: ianh
Date: 2008-02-26 01:37:57 -0800 (Tue, 26 Feb 2008)
New Revision: 1251
Modified:
index
source
Log:
[e] (0) Fix cross-refs to sectioning content; remove out-of-date reference to differences between xhtml and html content models for <p>.
Modified: index
===================================================================
--- index 2008-02-26 09:19:36 UTC (rev 1250)
+++ index 2008-02-26 09:37:57 UTC (rev 1251)
@@ -8192,11 +8192,12 @@
<p id=applyToSection>Some elements, for example <code><a
href="#address">address</a></code> elements, are scoped to their nearest
- ancestor sectioning content. For such elements <var title="">x</var>, the
- elements that apply to a <a href="#sectioning0">sectioning content</a>
- element <var title="">e</var> are all the <var title="">x</var> elements
- whose nearest <a href="#sectioning0">sectioning content</a> ancestor is
- <var title="">e</var>.
+ ancestor <a href="#sectioning0">sectioning content</a>. For such elements
+ <var title="">x</var>, the elements that apply to a <a
+ href="#sectioning0">sectioning content</a> element <var title="">e</var>
+ are all the <var title="">x</var> elements whose nearest <a
+ href="#sectioning0">sectioning content</a> ancestor is <var
+ title="">e</var>.
<h4 id=the-body><span class=secno>3.8.1 </span>The <dfn
id=body0><code>body</code></dfn> element</h4>
@@ -8732,19 +8733,22 @@
be included with other information in a <code><a
href="#footer">footer</a></code> element.
- <p>To determine the contact information for a sectioning element (such as a
- document's <code><a href="#body0">body</a></code> element, which would
- give the contact information for the page), UAs must collect all the
- <code><a href="#address">address</a></code> elements that <a
- href="#applyToSection">apply</a> to that sectioning element and its
- ancestor sectioning elements. The contact information is the collection of
- all the information given by those elements.</p>
- <!--
- XXX exception for nested article elements? -->
+ <p>To determine the contact information for a <a
+ href="#sectioning0">sectioning content</a> element (such as a document's
+ <code><a href="#body0">body</a></code> element, which would give the
+ contact information for the page), UAs must collect all the <code><a
+ href="#address">address</a></code> elements that <a
+ href="#applyToSection">apply</a> to that <a href="#sectioning0">sectioning
+ content</a> element and its ancestor <a href="#sectioning0">sectioning
+ content</a> elements. The contact information is the collection of all the
+ information given by those elements.</p>
+ <!-- XXX
+ exception for nested article elements? -->
- <p class=note>Contact information for one sectioning element, e.g. an
- <code><a href="#aside">aside</a></code> element, does not apply to its
- ancestor elements, e.g. the page's <code><a href="#body0">body</a></code>.
+ <p class=note>Contact information for one <a href="#sectioning0">sectioning
+ content</a> element, e.g. an <code><a href="#aside">aside</a></code>
+ element, does not apply to its ancestor elements, e.g. the page's <code><a
+ href="#body0">body</a></code>.
<h4 id=headings><span class=secno>3.8.11 </span><dfn id=headings0>Headings
and sections</dfn></h4>
@@ -8759,14 +8763,15 @@
href="#rank">rank</a> start new (implied) sections, headers of lower <a
href="#rank">rank</a> start subsections that are part of the previous one.
- <p>Sectioning elements other than <code><a
- href="#blockquote">blockquote</a></code> are always considered subsections
- of their nearest ancestor element of <a href="#sectioning0">sectioning
- content,</a> regardless of what implied sections other headings may have
- created. However, <code><a href="#blockquote">blockquote</a></code>
- elements <em>are</em> associated with implied sections. Effectively,
- <code><a href="#blockquote">blockquote</a></code> elements act like
- sections on the inside, and act opaquely on the outside.
+ <p><a href="#sectioning0">Sectioning content</a> elements other than
+ <code><a href="#blockquote">blockquote</a></code> are always considered
+ subsections of their nearest ancestor element of <a
+ href="#sectioning0">sectioning content</a>, regardless of what implied
+ sections other headings may have created. However, <code><a
+ href="#blockquote">blockquote</a></code> elements <em>are</em> associated
+ with implied sections. Effectively, <code><a
+ href="#blockquote">blockquote</a></code> elements act like sections on the
+ inside, and act opaquely on the outside.
<div class=example>
<p>For the following fragment:</p>
@@ -8939,9 +8944,9 @@
there is one, then it gives the section's heading, of there isn't, the
section has no heading.
- <p>Sections are nested as in the hypothetical tree. If a sectioning element
- is a child of another, that means it is a subsection of that other
- section.
+ <p>Sections are nested as in the hypothetical tree. If a <a
+ href="#sectioning0">sectioning content</a> element is a child of another,
+ that means it is a subsection of that other section.
<p>When creating an interactive table of contents, entries should jump the
user to the relevant section element, if it was a real element in the
@@ -10872,8 +10877,8 @@
<p>The <code><a href="#dfn">dfn</a></code> element represents the defining
instance of a term. The <a href="#paragraph">paragraph</a>, <a href="#dl"
- title=dl>description list group</a>, or <span title="sectioning
- elements">section</span> that contains the <code><a
+ title=dl>description list group</a>, or <a href="#sectioning0"
+ title="sectioning content">section</a> that contains the <code><a
href="#dfn">dfn</a></code> element contains the definition for the term
given by the contents of the <code><a href="#dfn">dfn</a></code> element.
@@ -37714,18 +37719,6 @@
<p>For historical reasons, certain elements have extra restrictions beyond
even the restrictions given by their content model.
- <p>A <code><a href="#p">p</a></code> element must not contain <code><a
- href="#blockquote">blockquote</a></code>, <code><a
- href="#dl">dl</a></code>, <code><a href="#menu">menu</a></code>, <code><a
- href="#ol">ol</a></code>, <code><a href="#pre">pre</a></code>, <code><a
- href="#table">table</a></code>, or <code><a href="#ul">ul</a></code>
- elements, even though these elements are technically allowed inside
- <code><a href="#p">p</a></code> elements according to the content models
- described in this specification. (In fact, if one of those elements is put
- inside a <code><a href="#p">p</a></code> element in the markup, it will
- instead imply a <code><a href="#p">p</a></code> element end tag before
- it.)
-
<p>An <code>optgroup</code> element must not contain <code>optgroup</code>
elements, even though these elements are technically allowed to be nested
according to the content models described in this specification. (If an
Modified: source
===================================================================
--- source 2008-02-26 09:19:36 UTC (rev 1250)
+++ source 2008-02-26 09:37:57 UTC (rev 1251)
@@ -6616,11 +6616,11 @@
<p id="applyToSection">Some elements, for example
<code>address</code> elements, are scoped to their nearest ancestor
- sectioning content. For such elements <var title="">x</var>, the
- elements that apply to a <span>sectioning content</span> element
- <var title="">e</var> are all the <var title="">x</var> elements
- whose nearest <span>sectioning content</span> ancestor is <var
- title="">e</var>.</p>
+ <span>sectioning content</span>. For such elements <var
+ title="">x</var>, the elements that apply to a <span>sectioning
+ content</span> element <var title="">e</var> are all the <var
+ title="">x</var> elements whose nearest <span>sectioning
+ content</span> ancestor is <var title="">e</var>.</p>
<h4>The <dfn><code>body</code></dfn> element</h4>
@@ -7035,18 +7035,20 @@
<p>Typically, the <code>address</code> element would be included
with other information in a <code>footer</code> element.</p>
- <p>To determine the contact information for a sectioning element
- (such as a document's <code>body</code> element, which would give
- the contact information for the page), UAs must collect all the
- <code>address</code> elements that <a
- href="#applyToSection">apply</a> to that sectioning element and its
- ancestor sectioning elements. The contact information is the
- collection of all the information given by those elements.</p> <!--
- XXX exception for nested article elements? -->
+ <p>To determine the contact information for a <span>sectioning
+ content</span> element (such as a document's <code>body</code>
+ element, which would give the contact information for the page), UAs
+ must collect all the <code>address</code> elements that <a
+ href="#applyToSection">apply</a> to that <span>sectioning
+ content</span> element and its ancestor <span>sectioning
+ content</span> elements. The contact information is the collection
+ of all the information given by those elements.</p> <!-- XXX
+ exception for nested article elements? -->
- <p class="note">Contact information for one sectioning element, e.g.
- an <code>aside</code> element, does not apply to its ancestor
- elements, e.g. the page's <code>body</code>.</p>
+ <p class="note">Contact information for one <span>sectioning
+ content</span> element, e.g. an <code>aside</code> element, does
+ not apply to its ancestor elements, e.g. the page's
+ <code>body</code>.</p>
@@ -7061,13 +7063,14 @@
start new (implied) sections, headers of lower <span>rank</span>
start subsections that are part of the previous one.</p>
- <p>Sectioning elements other than <code>blockquote</code> are always
- considered subsections of their nearest ancestor element of
- <span>sectioning content,</span> regardless of what implied sections
- other headings may have created. However, <code>blockquote</code>
- elements <em>are</em> associated with implied sections. Effectively,
- <code>blockquote</code> elements act like sections on the inside,
- and act opaquely on the outside.</p>
+ <p><span>Sectioning content</span> elements other than
+ <code>blockquote</code> are always considered subsections of their
+ nearest ancestor element of <span>sectioning content</span>,
+ regardless of what implied sections other headings may have created.
+ However, <code>blockquote</code> elements <em>are</em> associated
+ with implied sections. Effectively, <code>blockquote</code> elements
+ act like sections on the inside, and act opaquely on the
+ outside.</p>
<div class="example">
@@ -7121,8 +7124,9 @@
for the section's nesting level.</p>
<p>Authors are also encouraged to explictly wrap sections in
- elements of <span>sectioning content</span>, instead of relying on the implicit sections
- generated by having multiple heading in one element of <span>sectioning content</span>.</p>
+ elements of <span>sectioning content</span>, instead of relying on
+ the implicit sections generated by having multiple heading in one
+ element of <span>sectioning content</span>.</p>
<div class="example">
<p>For example, the following is correct:</p>
@@ -7239,9 +7243,9 @@
gives the section's heading, of there isn't, the section has no
heading.</p>
- <p>Sections are nested as in the hypothetical tree. If a sectioning
- element is a child of another, that means it is a subsection of that
- other section.</p>
+ <p>Sections are nested as in the hypothetical tree. If a
+ <span>sectioning content</span> element is a child of another, that
+ means it is a subsection of that other section.</p>
<p>When creating an interactive table of contents, entries should
jump the user to the relevant section element, if it was a real
@@ -8960,7 +8964,7 @@
<p>The <code>dfn</code> element represents the defining instance of
a term. The <span>paragraph</span>, <span title="dl">description
list group</span>, or <span title="sectioning
- elements">section</span> that contains the <code>dfn</code> element
+ content">section</span> that contains the <code>dfn</code> element
contains the definition for the term given by the contents of the
<code>dfn</code> element.</p>
@@ -35141,15 +35145,6 @@
<p>For historical reasons, certain elements have extra restrictions
beyond even the restrictions given by their content model.</p>
- <p>A <code>p</code> element must not contain
- <code>blockquote</code>, <code>dl</code>, <code>menu</code>,
- <code>ol</code>, <code>pre</code>, <code>table</code>, or
- <code>ul</code> elements, even though these elements are technically
- allowed inside <code>p</code> elements according to the content
- models described in this specification. (In fact, if one of those
- elements is put inside a <code>p</code> element in the markup, it
- will instead imply a <code>p</code> element end tag before it.)</p>
-
<p>An <code>optgroup</code> element must not contain
<code>optgroup</code> elements, even though these elements are
technically allowed to be nested according to the content models
More information about the Commit-Watchers
mailing list