- From: Dieter Köhler <dieter.koehler@ppp.uni-bamberg.de>
- Date: Fri, 17 Mar 2000 10:34:27 +0100
- To: "Ray D. Whitmer" <rayw@imall.com>
- CC: "www-dom@w3.org" <www-dom@w3.org>
> Generally, removeAttribute is used when a user does not already have
> a reference to the node and, hence, will not be reusing it. Otherwise
> the user could have called removeAttributeNode. But removeAttribute
> still allows for reuse, since it does not explicitly delete. If the
> user hung on to a reference in some prior call, then it does not get
> deleted.
So what's the reason, why removeAttribute does not return the
attribute's reference? If des user does not already have a reference
it might be useful and convenient that he might have it afterwards.
BTW: If the applications mixes namespace and non-namespace methods for
adding nodes in the following code
MyAttr:= MyElement.getAttributeNode('xyz');
MyElement.removeAttribute('xyz');
the first line might return another node than the second removes.
--
=====================================================================
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 Friday, 17 March 2000 04:36:31 UTC