[Webkit-unassigned] [Bug 12881] setAttributeNode behavior when node was created with createAttributeNS

[bugzilla-daemon at webkit.org]

http://bugs.webkit.org/show_bug.cgi?id=12881


ap at webkit.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ap at webkit.org




------- Comment #1 from ap at webkit.org  2007-02-25 01:00 PDT -------
I believe WebKit is correct when preserving the namespace in
setAttributeNode().

As you mention in your b.m.o report, the spec doesn't say what
setAttributeNode() does for namespaced attributes. However, there is a
non-normative note that seems to make the intention clear, see section 1.1.8 of
DOM 2 Core (or section 1.3.3 of DOM 3 Core):

----------------------------------------------
Similarly, using Element.setAttributeNode(newAttr), one can set two attributes
(or more) that have different Node.nodeNames but the same Node.prefix and
Node.namespaceURI. In this case Element.getAttributeNodeNS(namespaceURI,
localName) will return either attribute, in an implementation dependent manner.
The only guarantee in such cases is that all methods that access a named item
by its nodeName will access the same item, and all methods which access a node
by its URI and local name will access the same node.
----------------------------------------------


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.