- From: <bugzilla@jessica.w3.org>
- Date: Sat, 15 Mar 2014 00:12:46 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25062
Bug ID: 25062
Summary: Add specialized serialization requirements for element
namespaces in XML/XMLNS
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: DOM Parsing and Serialization
Assignee: travil@microsoft.com
Reporter: travil@microsoft.com
QA Contact: public-webapps-bugzilla@w3.org
CC: mike@w3.org, www-dom@w3.org
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.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 15 March 2014 00:12:47 UTC