W3C home > Mailing lists > Public > public-html@w3.org > October 2009

Re: ISSUE-41/ACTION-97 decentralized-extensibility

From: Anne van Kesteren <annevk@opera.com>
Date: Mon, 19 Oct 2009 13:02:13 +0200
To: "Adrian Bateman" <adrianba@microsoft.com>, "Jonas Sicking" <jonas@sicking.cc>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, "Tony Ross" <tross@microsoft.com>, "public-html@w3.org" <public-html@w3.org>
Message-ID: <op.u11nlzmo64w2qv@annevk-t60>
On Sun, 18 Oct 2009 21:42:54 +0200, Adrian Bateman  
<adrianba@microsoft.com> wrote:
> I meant something like <widget:datepicker>, <widget:menubar>,  
> <widget:treecontrol>. This seems fairly common in JavaScript control  
> libraries and finding all instances of controls provided by the library  
> is necessary. Page start-up performance for this kind of behaviour is  
> important. Something like this is where you might also want to style  
> across elements with CSS as Tony suggested. Of course, this is only one  
> of the suggested use cases but I think it's a reasonably compelling one.

FWIW, I believe in quite a few engines class names would be even more  
performant. With getElementsByClassName() (not yet in IE I believe) you'd  
also have a convenient way to get them. They would also work better if you  
have e.g. child nodes that you do not want to see returned in the  
collection.

For a set of element names you could also use querySelector().


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Monday, 19 October 2009 11:02:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:50 GMT