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
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
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
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
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
Boris Zbarsky wrote:
That answers my complaint, but not my question: what is
queryScopedSelector supposed to do?
When it was originally added, it was supposed to handle all of the
pre-parsing of the selector to prepend :scope to each selector in the
group, including handling things like div,
Hi Cyril,
On Jan 7, 2010, at 15:59 , Cyril Concolato wrote:
sorry to put you on the spot, but I don't recall this being discussed by
WebApps
I know that a liaison was sent from MPEG to the W3C early may 2009 and that
the WG was informed.
Ah, do you have a pointer? I searched for MPEG-U in
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
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
Thanks for the clarifications Maciej. I don't have any objections to
WebApps taking on this work.
However, since this functionality is not within the scope of WebApps'
current Charter [Charter], if we do have consensus within the WG that
it should be added (and I can start a CfC to
On Sun, Jan 10, 2010 at 2:25 PM, Adam Barth w...@adambarth.com wrote:
I don't quite understand this part of that text:
[[
In this case, the request
sent by the user-agent is not a uniform request; however, the request
ultimately delivered to the resource host will be, since any
Hi Art,
On Jan 11, 2010, at 12:10 PM, Arthur Barstow wrote:
Thanks for the clarifications Maciej. I don't have any objections to
WebApps taking on this work.
However, since this functionality is not within the scope of
WebApps' current Charter [Charter], if we do have consensus within
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
On Mon, Jan 11, 2010 at 12:40 PM, Tyler Close tyler.cl...@gmail.com wrote:
On Sun, Jan 10, 2010 at 2:25 PM, Adam Barth w...@adambarth.com wrote:
More abstractly, why aren't we worrying about P misbehaving based on
the ambient authority in R (i.e., the Proxy-Authentication
information)? Why do
14 matches
Mail list logo
