hixie: If you move a node from an HTML doc to an XML doc, you can create nodes with names you otherwise could not. So we have to handle that case also. (whatwg r3951)

hixie: If you move a node from an HTML doc to an XML doc, you can create
nodes with names you otherwise could not. So we have to handle that case
also. (whatwg r3951)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3112&r2=1.3113&f=h
http://html5.org/tools/web-apps-tracker?from=3950&to=3951

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3112
retrieving revision 1.3113
diff -u -d -r1.3112 -r1.3113
--- Overview.html 22 Sep 2009 00:25:11 -0000 1.3112
+++ Overview.html 22 Sep 2009 00:32:16 -0000 1.3113
@@ -64709,6 +64709,10 @@
    COLON (":").</li> <!--(prefixes can get adjusted, so this isn't an
    excuse) -->
 
+   <li>A node with a <!--prefix or--> local name that does not match
+   the XML <code title="">Name</code> production. <a href="#refsXML">[XML]</a></li> <!--(again, prefixes can get
+   adjusted, so this isn't an excuse) -->
+
    <li>An <code>Attr</code> node, <code>Text</code> node,
    <code>CDATASection</code> node, <code>Comment</code> node, or
    <code>ProcessingInstruction</code> node whose data contains
@@ -64732,9 +64736,8 @@
 
   </ul><p class="note">These are the only ways to make a DOM
   unserializable. The DOM enforces all the other XML constraints; for
-  example, trying to set an attribute with a name that contains an
-  equals sign (=) will raise an <code><a href="#invalid_character_err">INVALID_CHARACTER_ERR</a></code>
-  exception.</p>
+  example, trying to append two elements to a <code>Document</code>
+  node will raise a <code><a href="#hierarchy_request_err">HIERARCHY_REQUEST_ERR</a></code> exception.</p>

Received on Tuesday, 22 September 2009 00:33:12 UTC