W3C home > Mailing lists > Public > public-webapi@w3.org > December 2006

Re: Selectors API naming

From: Anne van Kesteren <annevk@opera.com>
Date: Sun, 24 Dec 2006 16:53:52 +0100
To: Martijn <martijn.martijn@gmail.com>
Cc: "Web API WG (public)" <public-webapi@w3.org>
Message-ID: <op.tk2mf2kv64w2qv@id-c0020>

On Sun, 24 Dec 2006 16:45:20 +0100, Martijn <martijn.martijn@gmail.com>  
wrote:
>> Not if the old methods effectively become obsolete. True enough, they
>> return a live NodeList and so might be useful for some use cases but I
>> don't think that goes for the majority if you see the usage of such
>> methods on the web.
>
> So the plan of matchAll is to make getElementById and
> getElementsByTagName effectively obsolete? And that's why a different
> sort of name is justified?

I would think so. Also for the reasons pointed out by Maciej and Rob of  
course.


I don't think get() is vague at all in the context of the document object  
by the way. The document object is mainly used for accessing the DOM and  
besides that provides several constructor methods for manipulating it.  
(The constructor methods are probably used way less than innerHTML etc.)  
It doesn't seem weird at all to me to provide such a short method name  
there.


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Sunday, 24 December 2006 15:54:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:56 GMT