> On Sun, Feb 24, 2013 at 8:18 AM, Anne van Kesteren <firstname.lastname@example.org> wrote:
>> Currently the XMLHttpRequest Standard special cases the condition
>> where the end user terminates the request. Given that there's less and
>> less likely to be UI for that kind of feature, does it still make
>> sense to expose this distinction from a network error in the API? I
>> think we should merge them.
Chrome(WebKit) and Firefox has ability to abort XHR requests:
With ESC key (in chrome it works while page is loading), also XHR is aborted while page unloading.
Chrome fires “abort”
Firefox fires “error”
In Firefox I can not distinguish network error from users abort(workarounds with page unloading detection will NOT work), but I have to show a warning message to the user when there is a network error.
I think, that
“abort” event is FOR that case.
this situation should be clearly spelled out in the spec