Can you make sure that it hasn't already been fixed in a nightly? http://code.jquery.com/jquery-nightly.js
A number of changes have gone into that method recently so it's likely already fixed. --John On Mon, Jul 27, 2009 at 10:53 AM, Christiaan Baartse <anotherh...@gmail.com>wrote: > > Seeing this went damn fast.. I just got 1 more change to 1.3.2 in the > jQuery.js I'm using. > > Its discribed in here > > http://groups.google.com/group/jquery-dev/browse_thread/thread/9c54083394a7df30 > that hack fixed it for me as well. > > Should I make a ticket for this? > > > On 27 jul, 15:22, John Resig <jere...@gmail.com> wrote: > > Too late:http://dev.jquery.com/changeset/6511 > > > > --John > > > > On Mon, Jul 27, 2009 at 9:21 AM, Andrea Giammarchi < > > > > andrea.giammar...@gmail.com> wrote: > > > I am posting a patch ;-) > > > > > On Mon, Jul 27, 2009 at 2:19 PM, John Resig <jere...@gmail.com> wrote: > > > > >> Err, wait - no it wouldn't. Nevermind. > > > > >> --John > > > > >> On Mon, Jul 27, 2009 at 9:18 AM, John Resig <jere...@gmail.com> > wrote: > > > > >>> Your solution doesn't appear to be correct: > > >>> ((elem.ownerDocument || elem).documentElement || false).nodeName > > > > >>> That could result in false.nodeName - which would cause an exception. > > > > >>> --John > > > > >>> On Mon, Jul 27, 2009 at 9:11 AM, Andrea Giammarchi < > > >>> andrea.giammar...@gmail.com> wrote: > > > > >>>> ((elem.ownerDocument || elem).documentElement || false).nodeName > > > --~--~---------~--~----~------------~-------~--~----~ 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 jquery-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
