+1
Thanks for all the help!
So, does this mean a mootools committer needs to file this as a bug,
or should/can I?
Also, on a small selector tangent, I think there is a bug with
the :contains() pseudo selector. For example, lets say you have this
markup:
<a href="foo" title="A link">Click Me</a>
So a selector like this should work: $$('a:contains(Click Me)') ,
right? It doesnt for me. Only this works: $$('a:contains(Click)') .
Same thing for attribute selectors. This doesnt work: $$("a[title=A
link]"). Rather, I have to do this: $$("a[title*=A link]").
I wrote a post about this a couple months back. Is this a bug too?
Does it need to be logged?
I would like to be more helpful in documenting these types of things.
Thanks
Jacob
On Apr 3, 6:01 am, daKmoR <[email protected]> wrote:
> On Apr 3, 10:37 am, Tom Occhino <[email protected]> wrote:
>
> > I think we should probably tweak match to return false as the base
> > case... If you pass no selector or an undefined / null selector, it
> > would make sense to return false imo..
>
> +1
