Hi John,
I'll take your word for it. I was just thinking it might of been a
quick solution as perhaps there are others out there doing the same.
As for the reasoning behind it there wasn't really any; just a curious
attempt while playing with the selectors.
I do however apprecate your feedback though :)
Cheers,
Mat.
On Oct 4, 12:17 am, "John Resig" <[EMAIL PROTECTED]> wrote:
> I don't think that this is really something that we can guarantee -
> especially as we start to move into using new selector engines like
> querySelectorAll which don't support DOM Element expandos at all.
>
> Why are you looking to introspect into DOM 0 event handlers? Surely
> there would be a better way of finding the elements that you'd want to
> locate.
>
> --John
>
> On Thu, Oct 2, 2008 at 10:11 PM, Mat Brennan <[EMAIL PROTECTED]> wrote:
>
> > Hello all,
>
> > Amazing library but one thing i've found and this might be me being
> > niggly is the inconsistency in the selector engine.
>
> > If i have the following selector:
> > $("[onclick^='fred']") - will return an error z.indexOf is not a
> > function.
> > however the camel case variant works. ($("[onClick^='fred']"))
>
> > This rings true with nearly all 'on' handlers.
>
> > I did a little debugging myself and it turns out that if the return
> > value is of type 'function' then that's when the error occurs. my
> > suggestion is that if the return value is function then it should be
> > cast back to a string so that the string based methods can do their
> > thing.
>
> > Would this be correct?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-dev@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
