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

Re: [selectors-api] Introduction with more background

From: Karl Dubost <karl@w3.org>
Date: Wed, 27 Sep 2006 16:00:14 +0900
Message-Id: <D91EE528-F6E9-493F-96EE-81DA04FAA3F2@w3.org>
Cc: "Web APIs WG (public)" <public-webapi@w3.org>
To: Anne van Kesteren <annevk@opera.com>

Le 19 sept. 06 à 19:55, Anne van Kesteren a écrit :
> On Wed, 26 Jul 2006 07:30:05 -0000, <karl@w3.org> wrote:
>> About http://www.w3.org/TR/2006/WD-selectors-api-20060525/ 
>> #introduction
>> 	[[[
>> 	It is often desirable to perform script and or
>> 	DOM operations on a specific set of elements in a document.
>> 	]]]
>> What are the benefits?
>> Why is it important?
>> How it makes the life of developers easier?
> It makes it easier to select a set of elements based on certain  
> criteria (for example all <div> elements with a class of example)  
> in a way that's consistent with how people are matching elements in  
> CSS for instance.
> So instead of having to filter what getElementsByTagName returns  
> you can directly filter it in the query. And given that  
> implementations of Selectors are claimed to be pretty efficient  
> it's expected this will be pretty efficient as well and most likely  
> faster than a custom implementation of it.

The comment was not correctly framed, explained. Thanks for the  
explanation, but put it in the prose of the specification. Questions  
were here to foster a more detailed introduction giving context and  
inviting developers to understand the benefits of the technology.

Please update the introduction.

Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager, QA Activity Lead
   QA Weblog - http://www.w3.org/QA/
      *** Be Strict To Be Cool ***
Received on Wednesday, 27 September 2006 07:01:54 UTC

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