I think a couple of those features are pretty low priority:
- I don't see the point of collective queries on NodeLists.
Are there any references for the proposal?
Otherwise I can't think of any useful queries that can't already be
achieved with a single querySelectorAll().
- Filtering NodeLists is trivial once we get matchesSelector().
Sean
Lachlan Hunt wrote:
Hi,
I'm planning to look at beginning work on Selectors API v2 soon to
add a number of requested features that didn't make it into the first
version. This e-mail is a summary of what is being considered, and is
intended to start discussion about which ones are really worth
focussing on, and how to ensure they address the use cases appropriately.
*Matches Selector*
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5865
*Filtering NodeLists*
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5864
*Scoped Queries*
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5860
*Collective Queries on NodeLists*
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7707
*Namespace Prefix Resolution*
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6290
