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

Re: Proposal: getElementsBySelector()

From: Anne van Kesteren <annevk@opera.com>
Date: Sun, 22 Apr 2007 11:09:35 +1000
To: "Jonas Sicking" <jonas@sicking.cc>, "Web APIs WG" <public-webapi@w3.org>
Message-ID: <op.tq5ut9cj64w2qv@id-c0020>

On Sat, 21 Apr 2007 09:28:22 +1000, Jonas Sicking <jonas@sicking.cc> wrote:
> Anne van Kesteren wrote:
>>  Given the input from Björn I suppose there's no real need for a method  
>> that returns a single element node (assuming implementations make that  
>> optimization). Given that, I propose we rename .getAll() to  
>> .getElementsBySelector() and drop .get() (on both Document and Element).
> I don't actually think it will be possible to make this optimization. In  
> the past we talked about mapping the StaticNodeList interface in the  
> ECMAScript bindings to a normal ECMA array. And possibly do the same  
> thing in other languages such as Java. This means that we can't use a  
> custom class that performs the lazy evaluation.
> Though looking at the latest version of the spec it looks like  
> StaticNodeList does not map to arrays, was that idea dropped or is it  
> just not in the spec yet?

I dropped the idea for now until someone gets around to writing the  
ECMAScript DOM binding(s) specification.

Anne van Kesteren
Received on Sunday, 22 April 2007 01:09:52 UTC

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