W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

Re: [DOM4] Remove Node.isSameNode

From: Jonas Sicking <jonas@sicking.cc>
Date: Fri, 9 Sep 2011 18:02:23 -0700
Message-ID: <CA+c2ei8b7F2=OmshrRBHz7VRhaWOFjSZSoyEOQwRM70Jxe-aGQ@mail.gmail.com>
To: Charles Pritchard <chuck@jumis.com>
Cc: Sean Hogan <shogun70@westnet.com.au>, Webapps WG <public-webapps@w3.org>
On Fri, Sep 9, 2011 at 3:42 PM, Charles Pritchard <chuck@jumis.com> wrote:
> On Sep 9, 2011, at 2:27 PM, Sean Hogan <shogun70@westnet.com.au> wrote:
>
>> On 10/09/11 3:21 AM, Jonas Sicking wrote:
>>> It's a completely useless function. It just implements the equality
>>> operator. I believe most languages have a equality operator already.
>>> Except Brainfuck [1]. But the DOM isn't implementable in Brainfuck
>>> anyway as it doesn't have objects, so I'm ok with that.
>>>
>>> [1] http://en.wikipedia.org/wiki/Brainfuck
>>>
>>
>> If a DOM implementation returns  node-wrappers instead of exposing the actual nodes then you could end up with different node-refs for the same node. I'm not sure whether that violates other requirements of the spec.
>
> A similar method is present in the JS libs too, like jQuery. If it is necessary, is a Node.isSameType useful?

I take it you mean "isSameNode", right?

Do you have a pointer to the jQuery function?

/ Jonas
Received on Saturday, 10 September 2011 01:03:20 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:47 GMT