#10906 closed bug (wontfix)
ajaxStop event not fired when one of the ajax success throw exception
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | low | Milestone: | None |
Component: | ajax | Version: | 1.7.1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
Example here:
The problem is that there is no error shown in console. The return callback seems to be try-catch-ed, making it difficult to debug.
Change History (6)
comment:1 Changed 11 years ago by
Owner: | set to [email protected]… |
---|---|
Status: | new → pending |
comment:3 Changed 11 years ago by
Status: | new → pending |
---|
jQuery does not support dev browser versions, since they might during development. Can you reproduce it on any stable browser?
comment:4 Changed 11 years ago by
Status: | pending → new |
---|
Cannot reproduce the bug in other stable browser.
comment:5 Changed 11 years ago by
Component: | unfiled → ajax |
---|---|
Priority: | undecided → low |
Resolution: | → wontfix |
Status: | new → closed |
Closing this as a wontfix. Can be opened if this still occurs when the stable version is released.
comment:6 Changed 10 years ago by
I was surprised this was the only page I could find on this issue. Generally that means I'm doing something wrong :-)
But running this slightly improved fiddle:
causes both stable IE9 and FF18 to not trigger the ajaxStop event.
Shouldn't the Ajax event handlers act "decoupled" and be executed in a try...catch...finally block, like this?
try { successCallback(); } // IE8 needs an explicit catch block catch (e) { throw e; } finally { triggerAjaxComplete(); }
Or is throwing an exception and re-throwing to some exception handler lower in the stack not how things are done in the Javascript world?
What browser and version are you using?
I tried the fiddle on Chrome 15 and Firefox 8, and correctly got the error in console: uncaught exception: Error in success function