Re: Publishing Selectors API Level 2 as an FPWD?

2010-01-11 Thread Jonas Sicking
On Sun, Jan 10, 2010 at 11:40 PM, Boris Zbarsky bzbar...@mit.edu wrote: On 1/11/10 1:24 AM, Sean Hogan wrote: That's correct. jQuery's $(element).find(div) is the equivalent of SelectorsAPI2's element.querySelectorAll(:scope div) or So in fact jquery can simply implement Element.find in

Re: Publishing Selectors API Level 2 as an FPWD?

2010-01-11 Thread Lachlan Hunt
Boris Zbarsky wrote: On 1/10/10 11:58 PM, Sean Hogan wrote: Even if jQuery deprecates non-standard selectors, the current spec for queryScopedSelector*() doesn't support the jQuery implicitly scoped selector *. As I understand it, jquery selectors on elements are always scoped in the sense

Re: Publishing Selectors API Level 2 as an FPWD?

2010-01-11 Thread Sean Hogan
On 11/01/10 8:55 PM, Lachlan Hunt wrote: In the following forms :scope is misleading: element.queryScopedSelector(:scope + *) element.queryScopedSelector(:scope ~ *) What's misleading about that? :scope would match the context node (what the element variable points to), and would return

Re: Publishing Selectors API Level 2 as an FPWD?

2010-01-11 Thread Boris Zbarsky
On 1/11/10 4:55 AM, Lachlan Hunt wrote: When there's no reference nodes passed and no :scope selector used, the behaviour of querySelector and querySelectorAll is unchanged from v1. If there is a :scope selector used, then it matches the context node. If there are also additional reference nodes

Re: Publishing Selectors API Level 2 as an FPWD?

2010-01-11 Thread Sean Hogan
On 11/01/10 6:40 PM, Boris Zbarsky wrote: On 1/11/10 1:24 AM, Sean Hogan wrote: That's correct. jQuery's $(element).find(div) is the equivalent of SelectorsAPI2's element.querySelectorAll(:scope div) or So in fact jquery can simply implement Element.find in terms of querySelectorAll by just

Re: Publishing Selectors API Level 2 as an FPWD?

2010-01-11 Thread Boris Zbarsky
On 1/11/10 12:13 PM, Boris Zbarsky wrote: I do wonder how useful queryScopedSelector is, since it can be implemented easily via querySelector... I guess the main value is in fact in situations when one is given a selector string already and not in situations where one is writing one's own

Re: Publishing Selectors API Level 2 as an FPWD?

2010-01-11 Thread Lachlan Hunt
Sean Hogan wrote: In summary, the proposed :scope pseudo-class only acts as a scope for the query in special cases, not in the general case. Yes, I'm aware of that. That was basically my reasoning for attempting to change it to :reference, but that name wasn't particularly well received

Re: Publishing Selectors API Level 2 as an FPWD?

2010-01-11 Thread Sean Hogan
On 12/01/10 5:30 AM, Lachlan Hunt wrote: Sean Hogan wrote: In summary, the proposed :scope pseudo-class only acts as a scope for the query in special cases, not in the general case. Yes, I'm aware of that. That was basically my reasoning for attempting to change it to :reference, but that

Re: Publishing Selectors API Level 2 as an FPWD?

2010-01-10 Thread Sean Hogan
On 8/01/10 1:19 AM, Lachlan Hunt wrote: Hi, Now that Selectors API Level 1 is published and basically all but finalised (just waiting for some implementations to be officially released before taking it to REC), can we publish Selectors API Level 2 as an FPWD? It would be useful to have it

Re: Publishing Selectors API Level 2 as an FPWD?

2010-01-10 Thread Lachlan Hunt
Sean Hogan wrote: On 8/01/10 1:19 AM, Lachlan Hunt wrote: can we publish Selectors API Level 2 as an FPWD? http://dev.w3.org/2006/webapi/selectors-api2/ FYI, it seems the whole Status of this Document hasn't been updated for Selectors-API2. Yeah, that will get fixed up when I get the spec

Re: Publishing Selectors API Level 2 as an FPWD?

2010-01-10 Thread Sean Hogan
On 11/01/10 8:29 AM, Lachlan Hunt wrote: Sean Hogan wrote: On 8/01/10 1:19 AM, Lachlan Hunt wrote: can we publish Selectors API Level 2 as an FPWD? http://dev.w3.org/2006/webapi/selectors-api2/ I can't see the value of queryScopedSelector*() methods. The original rationale was that JS

Re: Publishing Selectors API Level 2 as an FPWD?

2010-01-10 Thread Boris Zbarsky
On 1/10/10 11:58 PM, Sean Hogan wrote: Even if jQuery deprecates non-standard selectors, the current spec for queryScopedSelector*() doesn't support the jQuery implicitly scoped selector *. As I understand it, jquery selectors on elements are always scoped in the sense that they behave

Re: Publishing Selectors API Level 2 as an FPWD?

2010-01-10 Thread Sean Hogan
On 11/01/10 4:19 PM, Boris Zbarsky wrote: On 1/10/10 11:58 PM, Sean Hogan wrote: Even if jQuery deprecates non-standard selectors, the current spec for queryScopedSelector*() doesn't support the jQuery implicitly scoped selector *. As I understand it, jquery selectors on elements are always

Re: Publishing Selectors API Level 2 as an FPWD?

2010-01-10 Thread Sean Hogan
On 11/01/10 5:24 PM, Sean Hogan wrote: On 11/01/10 4:19 PM, Boris Zbarsky wrote: On 1/10/10 11:58 PM, Sean Hogan wrote: Even if jQuery deprecates non-standard selectors, the current spec for queryScopedSelector*() doesn't support the jQuery implicitly scoped selector *. As I understand it,

Re: Publishing Selectors API Level 2 as an FPWD?

2010-01-10 Thread Boris Zbarsky
On 1/11/10 1:24 AM, Sean Hogan wrote: That's correct. jQuery's $(element).find(div) is the equivalent of SelectorsAPI2's element.querySelectorAll(:scope div) or So in fact jquery can simply implement Element.find in terms of querySelectorAll by just prepending :scope to the selector string,