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

Re: [DOM4] Remove Node.isSameNode

From: Charles Pritchard <chuck@jumis.com>
Date: Fri, 9 Sep 2011 15:42:25 -0700
Message-Id: <424DDC32-14C8-400B-8C3A-7A3F3F54F5B3@jumis.com>
Cc: Jonas Sicking <jonas@sicking.cc>, Webapps WG <public-webapps@w3.org>
To: Sean Hogan <shogun70@westnet.com.au>




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
>> 
>> / Jonas
>> 
>> 
> 
> 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?
Received on Friday, 9 September 2011 22:42:56 GMT

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