Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
[e] (0) Comment out mentions of entities that are no longer relevant …
…(DOM Core dropped them).

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=13980

git-svn-id: http://svn.whatwg.org/webapps@6699 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Oct 19, 2011
1 parent c1144ac commit 508037b
Show file tree
Hide file tree
Showing 3 changed files with 26 additions and 15 deletions.
16 changes: 10 additions & 6 deletions complete.html
Expand Up @@ -3730,7 +3730,8 @@ <h4 id=conformance-classes><span class=secno>2.2.1 </span>Conformance classes</h
one of these two formats, although supporting both is
encouraged.</p>

<p id=entity-references>The language in this specification assumes
<!--(DOM Core doesn't have entity references
<p id="entity-references">The language in this specification assumes
that the user agent expands all entity references, and therefore
does not include entity reference nodes in the DOM. If user agents
do include entity reference nodes in the DOM, then user agents must
Expand All @@ -3741,6 +3742,7 @@ <h4 id=conformance-classes><span class=secno>2.2.1 </span>Conformance classes</h
well. Entity references to unknown entities must be treated as if
they contained just an empty text node for the purposes of the
algorithms defined in this specification.</p>
--><!--ENTITY-->

<p>Some conformance requirements are phrased as requirements on
elements, attributes, methods or objects. Such requirements fall
Expand Down Expand Up @@ -11314,8 +11316,9 @@ <h4 id=content-models><span class=secno>3.2.5 </span><dfn>Content models</dfn></
sections, for the purposes of determining if an element matches its
content model or not, <a href=#text-node title="text
node"><code>CDATASection</code> nodes in the DOM are treated as
equivalent to <code>Text</code> nodes</a>, and <a href=#entity-references>entity reference nodes are treated as if
they were expanded in place</a>.</p>
equivalent to <code>Text</code> nodes</a><!--, and <a
href="#entity-references">entity reference nodes are treated as if
they were expanded in place</a>--><!--ENTITY-->.</p>

<p>The <a href=#space-character title="space character">space characters</a> are
always allowed between elements. User agents represent these
Expand Down Expand Up @@ -92029,10 +92032,11 @@ <h3 id=serializing-html-fragments><span class=secno>13.3 </span>Serializing HTML

<li><p>The result of the algorithm is the string <var title="">s</var>.</li>

</ol><p class=note>Entity reference nodes are <a href=#entity-references>assumed to be expanded</a> by the user
</ol><!--
<p class="note">Entity reference nodes are <a
href="#entity-references">assumed to be expanded</a> by the user
agent, and are therefore not covered in the algorithm above.</p>

<p class=warning>It is possible that the output of this algorithm, if
--><!--ENTITY--><p class=warning>It is possible that the output of this algorithm, if
parsed with an <a href=#html-parser>HTML parser</a>, will not return the
original tree structure.</p>

Expand Down
16 changes: 10 additions & 6 deletions index
Expand Up @@ -3730,7 +3730,8 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
one of these two formats, although supporting both is
encouraged.</p>

<p id=entity-references>The language in this specification assumes
<!--(DOM Core doesn't have entity references
<p id="entity-references">The language in this specification assumes
that the user agent expands all entity references, and therefore
does not include entity reference nodes in the DOM. If user agents
do include entity reference nodes in the DOM, then user agents must
Expand All @@ -3741,6 +3742,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
well. Entity references to unknown entities must be treated as if
they contained just an empty text node for the purposes of the
algorithms defined in this specification.</p>
--><!--ENTITY-->

<p>Some conformance requirements are phrased as requirements on
elements, attributes, methods or objects. Such requirements fall
Expand Down Expand Up @@ -11314,8 +11316,9 @@ background: transparent"&gt;blue&lt;/span&gt;.&lt;/p&gt;</pre>
sections, for the purposes of determining if an element matches its
content model or not, <a href=#text-node title="text
node"><code>CDATASection</code> nodes in the DOM are treated as
equivalent to <code>Text</code> nodes</a>, and <a href=#entity-references>entity reference nodes are treated as if
they were expanded in place</a>.</p>
equivalent to <code>Text</code> nodes</a><!--, and <a
href="#entity-references">entity reference nodes are treated as if
they were expanded in place</a>--><!--ENTITY-->.</p>

<p>The <a href=#space-character title="space character">space characters</a> are
always allowed between elements. User agents represent these
Expand Down Expand Up @@ -92029,10 +92032,11 @@ document.body.appendChild(text);

<li><p>The result of the algorithm is the string <var title="">s</var>.</li>

</ol><p class=note>Entity reference nodes are <a href=#entity-references>assumed to be expanded</a> by the user
</ol><!--
<p class="note">Entity reference nodes are <a
href="#entity-references">assumed to be expanded</a> by the user
agent, and are therefore not covered in the algorithm above.</p>

<p class=warning>It is possible that the output of this algorithm, if
--><!--ENTITY--><p class=warning>It is possible that the output of this algorithm, if
parsed with an <a href=#html-parser>HTML parser</a>, will not return the
original tree structure.</p>

Expand Down
9 changes: 6 additions & 3 deletions source
Expand Up @@ -2641,6 +2641,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
one of these two formats, although supporting both is
encouraged.</p>

<!--(DOM Core doesn't have entity references
<p id="entity-references">The language in this specification assumes
that the user agent expands all entity references, and therefore
does not include entity reference nodes in the DOM. If user agents
Expand All @@ -2652,6 +2653,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
well. Entity references to unknown entities must be treated as if
they contained just an empty text node for the purposes of the
algorithms defined in this specification.</p>
--><!--ENTITY-->

<p>Some conformance requirements are phrased as requirements on
elements, attributes, methods or objects. Such requirements fall
Expand Down Expand Up @@ -11655,9 +11657,9 @@ background: transparent">blue&lt;/span>.&lt;/p></pre>
sections, for the purposes of determining if an element matches its
content model or not, <span title="text
node"><code>CDATASection</code> nodes in the DOM are treated as
equivalent to <code>Text</code> nodes</span>, and <a
equivalent to <code>Text</code> nodes</span><!--, and <a
href="#entity-references">entity reference nodes are treated as if
they were expanded in place</a>.</p>
they were expanded in place</a>--><!--ENTITY-->.</p>

<p>The <span title="space character">space characters</span> are
always allowed between elements. User agents represent these
Expand Down Expand Up @@ -104282,10 +104284,11 @@ document.body.appendChild(text);
title="">s</var>.</p></li>

</ol>

<!--
<p class="note">Entity reference nodes are <a
href="#entity-references">assumed to be expanded</a> by the user
agent, and are therefore not covered in the algorithm above.</p>
--><!--ENTITY-->

<p class="warning">It is possible that the output of this algorithm, if
parsed with an <span>HTML parser</span>, will not return the
Expand Down

0 comments on commit 508037b

Please sign in to comment.