Bug Tracker

Opened 9 years ago

Closed 9 years ago

#7254 closed bug

jQuery-1.4.2.js giving unresponsive script error in firefox

Reported by: Kotawala_Adnan@… Owned by: Kotawala_Adnan@…
Priority: undecided Milestone: 1.5
Component: ajax Version: 1.4.3
Keywords: Cc:
Blocked by: Blocking:

Description

jQuery-1.4.2.js giving unresponsive script error in firefox when my page contain a very large data.

Change History (5)

comment:1 Changed 9 years ago by addyosmani

Owner: set to Kotawala_Adnan@…
Status: newpending

Please submit a valid test case that shows us this error being reproduced. Also, note that we have a new version of the core out (1.4.3) which you can download over at jQuery.com. If your error is still being experienced with it and we find the test case is indeed correct, we'll investigate further.

comment:2 in reply to:  1 Changed 9 years ago by anonymous

Thanks for your reply.

So now I am using jquery-1.4.3.js following is my code.

--------------ajax call code start------------------------------------

$("#divAllQuestion").load("QuestionManagerAJAX.aspx?intCorpNo=" + intCorpNo + "&survey_no=" + intSurveyNo + "&intZarcaId=" + intZarcaId + "&page=" + intCurrPage + "&screenwidth=" + screen.width, function(response, status, xhr) {

if (status == "error") {

var msg = "Sorry but there was an error: "; $("#divAllQuestion").html(msg + xhr.status + " " + xhr.statusText);

} else if (status == "success") {

alert(status);

}

});

--------------ajax call code end--------------------------------------

in the above code "divAllQuestion" is a div in which I want to load the HTML returned by ajax call "QuestionManagerAJAX.aspx" is a page containing a large amount of HTML, say some 1000s of controls.

This code works fine in IE8 but gives Unresponsive script error in FireFox3+ and safari.

Thanks for Your reply once again Addyosmani. waiting for your response. Adnan Kotawala Zarca Interactive.

comment:3 Changed 9 years ago by Rick Waldron

Component: unfiledajax

Is there anyway you can post a test case for this?

It could just be that your app is overworking the DOM api while it attempts to create all the DOM elements your loading in.

comment:4 in reply to:  3 Changed 9 years ago by AKotawala

Replying to rwaldron:

Is there anyway you can post a test case for this?

It could just be that your app is overworking the DOM api while it attempts to create all the DOM elements your loading in.

Thanks for your reply Rwaldron

I have created a test solution in visual studio 2008, is there any way to attach it here so that you can have a look at it, to get the clear picture of the problem.

thanks once again

Thanks & Regards Adnan Kotawala Zarca Interactive.

comment:5 Changed 9 years ago by trac-o-bot

Status: pendingclosed

Automatically closed due to 14 days of inactivity.

Note: See TracTickets for help on using tickets.