- From: Dieter Köhler <dieter.koehler@ppp.uni-bamberg.de>
- Date: Tue, 07 Mar 2000 01:00:35 +0100
- To: keshlam@us.ibm.com, "www-dom@w3.org" <www-dom@w3.org>
> >a) removeAttribute and removeAttributeNS need a NOT_FOUND_ERR in order > >to operate in the same way as a NamedNodeMap. > > removeAttribute is Level 1. In Level 1, removing an attribute that doesn't > exist is a no-op. I don't think we can change that now without risk of > breaking existing code. What about a 'supports' attribute to allow a more flexible reaction? (That might also be a solution for some namespace problems discussed in other threads.) > Given that precedent, I'd rather have removeAttributeNS be consistant with > removeAttribute than with the NamedNodeMap. Consequence: When coding the API I cannot easily use a NamedNodeMap to store the attributes of an element. Well, I can catch the exception, but that is neither elegant nor fast. -- ===================================================================== Dieter Koehler, M. A. - dieter.koehler@ppp.uni-bamberg.de Mittlere Kaulberg 22, D-96049 Bamberg, +49(0)951-5190726 "http://www.philo.de/Philosophie-Seiten/": 1000+ Philosophie-Links "http://www.philo.de/VirtualLibrary/14.de.htm": Deutsche Philo-Links "http://www.philo.de/xml/": Open XML - XML-Komponenten fuer Delphi =====================================================================
Received on Monday, 6 March 2000 19:02:38 UTC