25062 2014-03-15 00:12:46 +0000 Add specialized serialization requirements for element namespaces in XML/XMLNS 2014-03-28 21:17:36 +0000 1 1 1 Unclassified WebAppsWG DOM Parsing and Serialization unspecified PC Windows NT RESOLVED FIXED P2 normal --- 1 travil travil mike www-dom public-webapps-bugzilla oldest_to_newest 102405 0 travil 2014-03-15 00:12:46 +0000 Some notes, while I was working on bug 24208: Firefox-as-reference: "<xml:div/>" == new XMLSerializer().serializeToString(document.createElementNS("http://www.w3.org/XML/1998/namespace", "foot:div")); * "xml" prefix trumps actual prefix for nodes in the XML namespace in the XML Serializer. (Same goes for nested elements with XML namespace: ...appendChild(document.createElementNS("http://www.w3.org/XML/1998/namespace", "toe:span")); "<xml:div><xml:span/></xml:div>" -- XMLSerializer "<foot:div><toe:span></toe:span></foot:div>" -- HTML Serializer uses QName Per DOM4: * XMLNS is tightly controlled (reserved) via createElementNS -- prefix/QName <-must match-> namespace * XML prefix -> XML namespace is controlled (reserved), but not vice-versa. Possible cases to handle: "<xmlns:div/>" == new XMLSerializer().serializeToString(document.createElementNS("http://www.w3.org/2000/xmlns/", "xmlns:div")); "<xmlns xmlns="http://www.w3.org/2000/xmlns/"/>" == new XMLSerializer().serializeToString(document.createElementNS("http://www.w3.org/2000/xmlns/", "xmlns")); * ASSERT: Follows generic serializer rules with regard to expansion/prefix use. 102792 1 travil 2014-03-23 00:05:01 +0000 Took care of this in most recent changes. 103125 2 travil 2014-03-28 21:17:36 +0000 Note, this was changeset: https://dvcs.w3.org/hg/innerhtml/rev/393c42a44e7f