no you should NOT use inline code, never again, even if you're playing
your life !
'Script taking to long' is usually a bad code design: infinite loop or
something like that.
Sorry Nicolas, that is not true - try to do 1000 mouseover binds or so on a
page and see how it goes for you. jQuery is fantastic but in some (very
few) situations it is not quite fast enough.
Obviously this is a "last resort" method but in a few cases it is necessary.
-- Josh
----- Original Message -----
From: "STuFF" <[EMAIL PROTECTED]>
To: "jQuery (English)" <jquery-en@googlegroups.com>
Sent: Tuesday, November 20, 2007 4:19 AM
Subject: [jQuery] Re: HELP: Debugging Issue
no you should NOT use inline code, never again, even if you're playing
your life !
'Script taking to long' is usually a bad code design: infinite loop or
something like that.
nicolas challeil
On Nov 19, 6:24 pm, "Josh Nathanson" <[EMAIL PROTECTED]> wrote:
A "script taking too long" error generally means that you are trying to
bind event handlers to too many elements, or just overloading the
capability of jquery in some way. You may want to look at going "old
school" and putting events inline in your html markup:
<a href="whatever" onclick="myfunction" onmouseover="myotherfunction"
onmouseout="anotherfunction">
-- Josh
----- Original Message -----
From: [EMAIL PROTECTED]
To: jquery-en@googlegroups.com
Sent: Sunday, November 18, 2007 9:07 PM
Subject: [jQuery] HELP: Debugging Issue
On one page, Firefox throws the "a script is taking too long" message.
On clicking 'Debug Script', it points to the following line of jQuery:
first.push(second[i]);
Which is in...
merge: function(first, second)
{
}
Assuming that there aren't any problems with jQuery, how can i find out
which code is throwing this error?
Thanks
Fahed
