I was curious for a different reason - because we recently adjusted how we
handle .status === 0 in $.ajax. But I agree that this should probably be an
abort failure.
--John
On Wed, Aug 12, 2009 at 10:27 AM, Andrea Giammarchi <
andrea.giammar...@gmail.com> wrote:
> John do you think it is an iss
I think browser aborting all xhr request onunload. You can can also
abort request if you press ESC while sending.
On Aug 12, 11:06 am, zacware wrote:
> Here's a sample to demo the issue:
>
> http://homepage.mac.com/zacware/xhr_bug/xhr_bug.htm
>
> We deployed our intranet using FireFox 1 and Fire
John do you think it is an issue? It sounds logical if error catch abort
operations as well.
Maybe I am missing something
On Wed, Aug 12, 2009 at 3:21 PM, John Resig wrote:
> I'm curious - what happens if you try the latest jQuery nightlies?
> http://code.jquery.com/jquery-nightly.js
>
> --John
I'm curious - what happens if you try the latest jQuery nightlies?
http://code.jquery.com/jquery-nightly.js
--John
On Wed, Aug 12, 2009 at 5:06 AM, zacware wrote:
>
> Here's a sample to demo the issue:
>
> http://homepage.mac.com/zacware/xhr_bug/xhr_bug.htm
>
> We deployed our intranet using F
Well, status 0 makes sense, you change URL before Ajax request is finished.
In few words is like a manual abort and jQuery correctly fires the error
event.
Accoridngly, I cannot spot a single problem here, can you?
On Wed, Aug 12, 2009 at 10:06 AM, zacware wrote:
>
> Here's a sample to demo th
