Bug Tracker

Ticket #5468 (closed bug: fixed)

Opened 5 years ago

Last modified 5 years ago

Bad URI causes ajaxStop and ajaxComplete not to fire

Reported by: mrspeaker Owned by:
Priority: minor Milestone: 1.4
Component: ajax Version: 1.3.2
Keywords: Cc:
Blocking: Blocked by:

Description

If you do an Ajax request that generates a NS_ERROR_DOM_BAD_URI (or anything else that gets caught in the try/catch) then the complete() function is never run - so ajaxStop and ajaxComplete do not fire (and jQuery.active does not get decremented)

Here is a test page:  http://www.mrspeaker.net/dev/jq/complete/ The call is to a " file:///" URI (the real reason I found this was running a request from the local filesystem that 404ed)

A possible patch is to simply call complete() in the catch block (diff included)

Attachments

complete.diff Download (383 bytes) - added by mrspeaker 5 years ago.

Change History

Changed 5 years ago by mrspeaker

comment:1 Changed 5 years ago by john

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.