may be change this line
jQuery(document).ready(function($) {
to this
$(function() {
On Fri, Jun 19, 2009 at 11:22 PM, James james.gp@gmail.com wrote:
Could this: delay(delayValue);
have anything to do with it?
In your code, if you comment out all the calls to CreateOnClickEvent,
I've pinpointed the script that's causing the timeout. Commenting
this script out resolves the issue. I don't see anything in this
script however that is out of place. I'd be curious if some better
trained eyes find something.
Thanks again for all of your help.
I've pinpointed the script that's causing the timeout. Commenting
this script out resolves the issue. I don't see anything in this
script however that is out of place. I'd be curious if some better
trained eyes find something.
Thanks again for all of your help.
I think it's the if/else if statement at the top. If I change the
last else if to just an else, I get a syntax error but no
unresponsive script error.
function mousedownSearchTracking(e) {
var $zone = $(this);
if (typeof (e.data.action) == undefined) {
if (typeof
what happens if you put an empty else {} after the last elseif?
On Jun 19, 10:33 am, bombaru bomb...@gmail.com wrote:
I think it's the if/else if statement at the top. If I change the
last else if to just an else, I get a syntax error but no
unresponsive script error.
function
Same result: Unresponsive script error
On Jun 19, 11:17 am, amuhlou amysch...@gmail.com wrote:
what happens if you put an empty else {} after the last elseif?
On Jun 19, 10:33 am, bombaru bomb...@gmail.com wrote:
I think it's the if/else if statement at the top. If I change the
last
What does the function for CreateOnClickEvent look like if you don't
mind posting that?
On Jun 19, 6:15 am, bombaru bomb...@gmail.com wrote:
Same result: Unresponsive script error
On Jun 19, 11:17 am, amuhlou amysch...@gmail.com wrote:
what happens if you put an empty else {} after the
That's part of Omniture tracking code. Looks like this:
function CreateOnClickEvent(sTitle, nEvarNumber, sValue) {
try {
var s2 = s_gi(s_account);
if (SetS2EvarValue(s2, nEvarNumber, sValue))
{
s2.linkTrackVars = 'eVar' + nEvarNumber;
Could this: delay(delayValue);
have anything to do with it?
In your code, if you comment out all the calls to CreateOnClickEvent,
does it make the page respond?
I think just by drilling in and testing like this, you'll be likely to
find the cause of the unresponsive script issues.
On Jun 19,
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:
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
try removing your custom scritps 1 by 1 until the error stops or reduces.
then post the script here when you find the right one.
note : do not trust specific lines as you are using a library there may be a
refference in a specific script causing this.
On Thu, Jun 18, 2009 at 11:18 PM, James
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
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
What were the version number of the older versions of jQuery you were
using?
On Jun 18, 11:50 am, waseem sabjee waseemsab...@gmail.com wrote:
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
That error has nothing to do with jQuery-1.3.2.js, it's one of your
scripts. You're missing a semi-colon or have some unclosed quotes, or
you're trying to use a function that doesn't exist. Are you using
Firefox with the Firebug plugin to debug? If not, do it, it should
give you a more detailed
@googlegroups.com
Subject: [jQuery] Re: Unresponsive script when navigating away
Oh and :checkbox is a shortcut for input[type=checkbox].
Karl Rudd
On Sat, Nov 1, 2008 at 6:05 PM, Karl Rudd [EMAIL PROTECTED] wrote:
Instead of doing the search each time, cache the selected objects
Thanks.! will try that
Regards,
Kai
Date: Sat, 1 Nov 2008 18:07:18 +1100
From: [EMAIL PROTECTED]
To: jquery-en@googlegroups.com
Subject: [jQuery] Re: Unresponsive script when navigating away
Oh and :checkbox is a shortcut for input[type=checkbox].
Karl Rudd
On Sat, Nov 1, 2008
Instead of doing the search each time, cache the selected objects.
script type=text/javascript
$(document).ready(function (){
var checkboxes = $('div[name=limit1] label
input[type=checkbox]');
checkboxes.bind('click',function(){
Oh and :checkbox is a shortcut for input[type=checkbox].
Karl Rudd
On Sat, Nov 1, 2008 at 6:05 PM, Karl Rudd [EMAIL PROTECTED] wrote:
Instead of doing the search each time, cache the selected objects.
script type=text/javascript
$(document).ready(function (){
var
Thanks for the explanation, Karl. That makes a lot of sense.
Your chunking solution does seem to prevent the unresponsive
script errors when the page is loading. However, I still get them
when I navigate away from the page -- I assume jquery is unbinding
all of the cluetips.
For that reason
Thanks to both Karls for your help!
I'll definitely try out the chunking method. Since I'd like to
understand what I'm implementing, can you briefly explain why this way
is better?
thanks,
az
On Apr 1, 4:59 pm, Karl Rudd [EMAIL PROTECTED] wrote:
You can initialise the tips in chunks.
JavaScript in browsers is single-threaded (and thank goodness for
that). So when JavaScript is running (in most browsers) everything
else is queuing up. When you break the code into chunks, via
setTimeout, you are (essentially) yielding control back to the main
event loop periodically, so it has
Hi az,
The only way I know of to deal with binding events to that many
elements directly without incurring huge costs (unresponsive script
errors, etc.) is to do it inline, as you suggested.
Another approach is event delegation, but I haven't set up the plugin
to take advantage of that
You can initialise the tips in chunks.
Instead of doing something like this:
$('a.tip').cluetip();
Do something like this:
$('a.tip').each(function() {
var t = $(this);
setTimeout( function() { t.cluetip(); }, 10 );
})
You'll still have a bit of a CPU usage spike but it shouldn't
Ah, great idea! thanks, Karl
--Karl
_
Karl Swedberg
www.englishrules.com
www.learningjquery.com
On Apr 1, 2008, at 7:59 PM, Karl Rudd wrote:
You can initialise the tips in chunks.
Instead of doing something like this:
$('a.tip').cluetip();
Do something like this:
26 matches
Mail list logo
