W3C home > Mailing lists > Public > public-html-diffs@w3.org > October 2011

hixie: Comment out mentions of entities that are no longer relevant (DOM Core dropped them). (whatwg r6699)

From: poot <cvsmail@w3.org>
Date: Wed, 19 Oct 2011 18:03:01 -0400
To: public-html-diffs@w3.org
Message-Id: <E1RGeE1-0004Jc-7G@jay.w3.org>
hixie: Comment out mentions of entities that are no longer relevant (DOM
Core dropped them). (whatwg r6699)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.5369&r2=1.5370&f=h
http://html5.org/tools/web-apps-tracker?from=6698&to=6699

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5369
retrieving revision 1.5370
diff -u -d -r1.5369 -r1.5370
--- Overview.html	19 Oct 2011 21:56:57 -0000	1.5369
+++ Overview.html	19 Oct 2011 22:00:43 -0000	1.5370
@@ -3052,17 +3052,6 @@
   one of these two formats, although supporting both is
   encouraged.</p>
 
-  <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
-  handle them as if they were fully expanded when implementing this
-  specification. For example, if a requirement talks about an
-  element's child text nodes, then any text nodes that are children of
-  an entity reference that is a child of that element would be used as
-  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>
 
   <p>Some conformance requirements are phrased as requirements on
   elements, attributes, methods or objects. Such requirements fall
@@ -9307,8 +9296,7 @@
   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>The <a href="#space-character" title="space character">space characters</a> are
+  equivalent to <code>Text</code> nodes</a>.<p>The <a href="#space-character" title="space character">space characters</a> are
   always allowed between elements. User agents represent these
   characters between elements in the source markup as text nodes in
   the DOM. Empty <a href="#text-node" title="text node">text nodes</a> and <a href="#text-node" title="text node">text nodes</a> consisting of just sequences of
@@ -63738,10 +63726,7 @@
 
    <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
-  agent, and are therefore not covered in the algorithm above.</p>
-
-  <p class="warning">It is possible that the output of this algorithm, if
+  </ol><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>
Received on Wednesday, 19 October 2011 22:03:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 19 October 2011 22:03:37 GMT