are you perhaps using an @ sign in any ajax posts or gets ?

On Thu, Jun 18, 2009 at 11:44 PM, bombaru <bomb...@gmail.com> wrote:

>
> Yes.  A lot of other scripts.  I have started to comment out the
> scripts one-by-one and will see if I can locate the offending one.  Is
> there any reason (that you might know of) why this is happening in
> 1.3.2 and not older versions of jQuery?
>
>
>
> On Jun 18, 5:18 pm, James <james.gp....@gmail.com> wrote:
> > Do you have other scripts running on the page aside from just jQuery?
> > Such as other scripts that rely on jQuery?
> >
> > On Jun 18, 11:00 am, bombaru <bomb...@gmail.com> wrote:
> >
> > > I switched to the development version of jQuery so I could actually
> > > see where the offending line was.  I'm still getting the same error,
> > > but obviously the line number has changed (which will be more
> > > helpful).  Sorry.
> >
> > > Here's the error in the development version:
> >
> > > Script:http://localhost/js/jquery/jquery-1.3.2.js:1988
> >
> > > Here's line 1988:
> >
> > > 1983 if (parent && (parent.sizcache !== doneName || !elem.nodeIndex))
> > > {
> > > 1984     var count = 0;
> > > 1985     for (node = parent.firstChild; node; node = node.nextSibling)
> > > {
> > > 1986         if (node.nodeType === 1) {
> > > 1987             node.nodeIndex = ++count;
> > > 1988         }
> > > 1989     }
> > > 1990     parent.sizcache = doneName;
> > > 1991 }
> >
> > > Again, any help will be much appreciated.
> >
> > > Thanks.
> >
> > > On Jun 18, 4:45 pm, bombaru <bomb...@gmail.com> wrote:
> >
> > > > Anyone know why I might be getting and "Unresponsive script" warning?
> > > > I'm running 1.3.2.min.  The Warning pops up and states the following:
> >
> > > > A script on this page may be busy, or may have stopped responding.
> > > > You can stop the script now, open the script in the debugger, or let
> > > > the script continue.
> >
> > > > Script:http://localhos/js/jquery/jquery-1.3.2.min.js:19
> >
> > > > This error is new since upgrading to jQuery 1.3.2.  Previous versions
> > > > of jQuery did not produce this error.
> >
> > > > Any help you can provide will be greatly appreciated.
> >
> > > > Thanks
>

Reply via email to