On 09.03.2009, at 01:44, Tobie Langel wrote:
We'll be shifting to Sizzle pretty soon, which afaik allows (or could
easily be modified to allow) both behaviours.
Maybe we can make this opt-in for an upcoming release.
That would be great, I can see both use cases. I also see that
With :self I could do:
$(x).select(':self .mixedcontent').each(...);
I don't have anything against :self, but I don't see why $(x).select
( .foo) shouldn't be legal syntax.
Right now this is the shortest I came up with, and it's not as concise
as I'm used to with Prototype:
On 8 Mar, 14:51, Marc Liyanage liyan...@gmail.com wrote:
From my experiments I get the impression that the select() context
element and all of its ancestors are completely taken out of the
selector match calculation.
Exaclty :)
It selects from elements INSIDE of given one. So it can find
On Mar 8, 2:51 pm, Marc Liyanage liyan...@gmail.com wrote:
I am wondering if this is a bug:
body id='body'
div id='foo' class='div_a'
span class='span_a'/span
div class='div_a'
span class='span_a'/span
Hi,
You might want to read John Resig's article[1] on
document.querySelectorAll.
Ideally, a :root or :self selector would be specified so as to avoid
this potential confusion.
For example:
$('foo').select(':self div.div_a span.span_a')
Best,
Tobie
[1]
On Mar 8, 5:34 pm, Quleczka qulec...@gazeta.pl wrote:
On 8 Mar, 14:51, Marc Liyanage liyan...@gmail.com wrote:
From my experiments I get the impression that the select() context
element and all of its ancestors are completely taken out of the
selector match calculation.
Exaclty :)
