Response title
This is preview!
Move this topic
.ajax()-error isn't fired in v1.4.2 ?! (v1.3.2 works fine..)
in Developing jQuery Core
•
2 years ago
hi all!
about two weeks ago i reported:
http://dev.jquery.com/ticket/6173
it's about that using
$.ajax({error: myCallback});
the "myCallback" isn't fired when the ajax-request is aborted (e.g. by hitting ESC)
i wonder if i am doing something wrong, however in jq1.3.2 it just works fine..
cheers,
-dpree
about two weeks ago i reported:
http://dev.jquery.com/ticket/6173
it's about that using
$.ajax({error: myCallback});
the "myCallback" isn't fired when the ajax-request is aborted (e.g. by hitting ESC)
i wonder if i am doing something wrong, however in jq1.3.2 it just works fine..
cheers,
-dpree
5
Replies(9)
I have the same problem, although I'm not manually aborting the request -- I request the page and then shut down the server so that Ajax calls should fail with "connection refused".
In JQuery 1.3.2, the "error" callback fires nicely.
In JQuery 1.4.2, the "success" callback fires instead (with data="", and XMLHttpRequest.status=0).
I guess it must be a race condition or something, since the "error" callback does fire when I place some breakpoints around the "ajax" function definiton in Firebug.
I'm not sure what to do next...
In the meantime I will keep using JQuery 1.3.2.
In JQuery 1.3.2, the "error" callback fires nicely.
In JQuery 1.4.2, the "success" callback fires instead (with data="", and XMLHttpRequest.status=0).
I guess it must be a race condition or something, since the "error" callback does fire when I place some breakpoints around the "ajax" function definiton in Firebug.
I'm not sure what to do next...
In the meantime I will keep using JQuery 1.3.2.
Leave a comment on robertjhunter's reply
workaround:
when i hit ESC in ff3.0.18 then success is triggered and then xhr.status==0, so u can do:
success: function(resp, textS, xhr) {
if (xhr.status) {
// everything ok
} else {
// it's actually an error
}
}
@robert
=> which browser do u use?
-dpree
when i hit ESC in ff3.0.18 then success is triggered and then xhr.status==0, so u can do:
success: function(resp, textS, xhr) {
if (xhr.status) {
// everything ok
} else {
// it's actually an error
}
}
@robert
=> which browser do u use?
-dpree
Leave a comment on ydpree's reply
Same problem here with jq 1.4.2, using Firefox 3.6.3
Leave a comment on sosh101's reply
Has anybody tested this with 1.5?
Leave a comment on jaubourg's reply
hm, would be interesting to know..
--dpree
--dpree
Kinda funny. I went to test this and found that $.ajax(url) was broken, but that has already been fixed for 1.5.1. Anyway, no, it seems aborting with the esc key does not produce the error callback.
Leave a comment on ydpree's reply
Did some more testing and it seems 1.3.2 did not produce the error callback either when aborting with the esc key. I think aborting with esc is a special case that is more of a "stop everything" than "stop xhr". Complete does not fire either and that's just weird.
Leave a comment on timmywil's reply
hm ESC did not work in 1.3.2 really? i think i should make also some tests, because i remember that i came across the whole problem just because when i upgraded (maybe from even an older than 1.3.2) jquery version the ESC hit stopped working in our application.
however i am not involved anymore in developing the application - so i don't care at the moment and my motivation is driven by pure technical interests :)
--dpree
Leave a comment on ydpree's reply
Change topic type
Link this topic
Provide the permalink of a topic that is related to this topic
Reply to ydpree's question
Statistics
- 9 Replies
- 6465 Views
- 4 Followers
