Skip to main content

Bug Tracker

Side navigation

#12611 closed bug (invalid)

Opened September 26, 2012 04:56AM UTC

Closed October 11, 2012 08:54AM UTC

ajax() calls success under certain failure conditions

Reported by: darius@dons.net.au Owned by: darius@dons.net.au
Priority: undecided Milestone: None
Component: unfiled Version: 1.4.2
Keywords: Cc:
Blocked by: Blocking:
Description

I have a page which uses ajax() to load some JSON like so..

    $.ajax({'url' : 'array-status.json', 'dataType' : 'json', 'data' : args,
	    'success' : updatestatus,
	    'error' : function(jqXHR, textStatus, errorThrown) {
		disable_spinner();
		$("#errortxt").html("Unable to load antenna data: " + jqXHR.status + " (" + jqXHR.statusText + ")");
	    },
	    'cache' : false
	   });
}

If I kill the web server (a flask instance) I find that the success call back is executed. If the backend is alive but returns an error it behaves as I expect (ie the error call back is executed).

The jqXHR looks like..

qXHR
XMLHttpRequest
abort: function () {
onabort: null
onerror: null
onload: null
onloadend: null
onloadstart: null
onprogress: null
onreadystatechange: function () {}
readyState: 4
response: ""
responseText: ""
responseType: ""
responseXML: null
status: 0
statusText: ""
upload: XMLHttpRequestUpload
withCredentials: false
__proto__: XMLHttpRequest

This is using Chrome 22.0.1229.64 beta.

Attachments (0)
Change History (2)

Changed September 27, 2012 01:33AM UTC by dmethvin comment:1

owner: → darius@dons.net.au
status: newpending

Can you try it on a released Chrome browser and see if the problem is still there? If not you should definitely be reporting this to the Chrome team and not here. Also, a complete test case would help.

Changed October 11, 2012 08:54AM UTC by trac-o-bot comment:2

resolution: → invalid
status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!