[html5] r6699 - [e] (0) Comment out mentions of entities that are no longer relevant (DOM Core d [...]

whatwg at whatwg.org whatwg at whatwg.org
Wed Oct 19 14:56:57 PDT 2011


Author: ianh
Date: 2011-10-19 14:56:56 -0700 (Wed, 19 Oct 2011)
New Revision: 6699

Modified:
   complete.html
   index
   source
Log:
[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

Modified: complete.html
===================================================================
--- complete.html	2011-10-19 21:53:04 UTC (rev 6698)
+++ complete.html	2011-10-19 21:56:56 UTC (rev 6699)
@@ -3730,7 +3730,8 @@
   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
@@ -3741,6 +3742,7 @@
   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
@@ -11314,8 +11316,9 @@
   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
@@ -92029,10 +92032,11 @@
 
    <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>
 

Modified: index
===================================================================
--- index	2011-10-19 21:53:04 UTC (rev 6698)
+++ index	2011-10-19 21:56:56 UTC (rev 6699)
@@ -3730,7 +3730,8 @@
   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
@@ -3741,6 +3742,7 @@
   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
@@ -11314,8 +11316,9 @@
   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
@@ -92029,10 +92032,11 @@
 
    <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>
 

Modified: source
===================================================================
--- source	2011-10-19 21:53:04 UTC (rev 6698)
+++ source	2011-10-19 21:56:56 UTC (rev 6699)
@@ -2641,6 +2641,7 @@
   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
@@ -2652,6 +2653,7 @@
   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
@@ -11655,9 +11657,9 @@
   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
@@ -104282,10 +104284,11 @@
    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




More information about the Commit-Watchers mailing list