W3C home > Mailing lists > Public > public-webapi@w3.org > July 2007

Re: Ambiguity in removeAttributeNode

From: Cameron McCormack <cam@mcc.id.au>
Date: Sat, 28 Jul 2007 16:05:20 +1000
To: Travis Leithead <travil@windows.microsoft.com>
Cc: public-webapi@w3.org, ian@hixie.ch, bjoern@hoehrmann.de, Chris Wilson <chris.wilson@microsoft.com>
Message-ID: <20070728060520.GB29468@arc.mcc.id.au>

Hi Travis.

Travis Leithead:
> We happened to notice an interesting behavior difference in
> removeAttributeNode recently, and an appeal to the standard didn't seem
> to help...
> IE fails in this example and triggers the try/catch. FF works, Opera
> also fails. It seems that some browser implementers deciphered the DOM
> Core spec::removeAttributeNode to mean that "object" comparison is used
> as the delete criteria, but others seem to only base it on the "name" of
> the Attr. 
> Is there hope in coming to harmony across implementations on this point?
> Or how should the spec be interpreted?

The description for removeAttributeNode does say:

  Removes the specified attribute node.

So it seems clear to me that it should remove only the exact Attr object
that was given, rather than any Attr on the object that has the same
name.  What text do you think is ambiguous?

WebKit’s behaviour is also the same as IE and Opera.  I’d say it’s a bug
in Firefox.


Cameron McCormack, http://mcc.id.au/
	xmpp:heycam@jabber.org  ▪  ICQ 26955922  ▪  MSN cam@mcc.id.au
Received on Saturday, 28 July 2007 06:05:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:24 UTC