W3C home > Mailing lists > Public > www-dom@w3.org > October to December 1999

Possible bug in specification of Element.setAttributeNS

From: David Ziegler <dziegler1@meteko.com>
Date: Tue, 12 Oct 1999 10:34:57 -0400 (EDT)
Message-ID: <003401bf14b7$69556cc0$19c0a8c0@meteko.com>
To: <www-dom@w3.org>
I am implementing the DOM2 core and ran across the following problem:

The attribute name parameter to Element.setAttributeNS is given as a localName so it is not possible using 
this API to define a new attribute that has a prefix.  When adding a new attribute that needs a prefix 
the user will then need to do a getAttributeNodeNS to get the attribute node and then do a setPrefix.
This is especially inconvenient given that the user often does not distinguish between defining a
new attribute and updating an existing one (in fact the api is defined to hide this distinction).

I propose that the name parameter be redefined as a qualified name.   This will solve this problem and
is also consistent with how attributes are created by the factory in Document.

Thank you for your time.

David Ziegler
Received on Wednesday, 13 October 1999 09:55:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:06 UTC