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

Re: [selectors api] Why two methods?

From: Jim Ley <jim@jibbering.com>
Date: Thu, 25 Jan 2007 19:52:00 -0000
Message-ID: <061e01c740ba$48318c90$59221f80@Sniff>
To: David Håsäther <hasather@gmail.com>, "Anne van Kesteren" <annevk@opera.com>
Cc: <public-webapi@w3.org>

"David Håsäther" <hasather@gmail.com>
> On 2007-01-25 20:42, Anne van Kesteren wrote:
>> On Thu, 25 Jan 2007 14:39:46 -0500, David Håsäther <hasather@gmail.com> 
>> wrote:
>>> Why does the Selectors API define two methods for retrieving nodes?
>>> I understand that there are speed gains by having a method that grabs
>>> just the first node, but how often do you want to do that? Don't you
>>> want to grab the second node as often? Or the last?
>> How do you mean?
> Sorry for not being clear.
> What I mean is, why does grabbing the first node deserve its own method? 
> Is that really a common thing to do, grabbing the first node? More common 
> than grabbing the second or last node for instance?

I do agree with this, there seems to be very few use cases where just 1 is 
useful and the user is not going to be able to use .getElementById instead.


Received on Thursday, 25 January 2007 19:52:39 UTC

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