Re: calling abort method on XMLHttpRequest instance fires onreadystatechange with readyState 4

Martin Honnen wrote:
> Boris Zbarsky wrote:
> 
>> See in particular 
>> https://bugzilla.mozilla.org/show_bug.cgi?id=218236#c11 for 
>> comparisons to IE 6.0 behavior.  Note the inconsistency in IE behavior 
>> depending on the value of readyState when abort() is called (1 and 2 
>> give different behavior).
> 
> I have played with variations of my test case, this variation
> <http://home.arcor.de/martin.honnen/mozillaBugs/XMLHttpRequest/abortChangesReadyState4ProgramIdDelay.html> 
> 
> which only calls abort using setTimeout with a configurable delay indeed 
> consistently for abort called on
>   readyState 1
>   program id Microsoft.XMLHTTP, Msxml2.XMLHTTP, Msxml2.XMLHTTP.3.0
>   delay 10 milliseconds
> shows readystatechange events as
>   1 -> 1 -> 4
> the abort sets readyState to 0 (and does that twice due to 1 -> 1 
> transition).
> 
> Those program ids above are all bound to MSXML 3 on my system, if I run 
> the same test with program ids for MSXML 4 or MSXML 5 or MSXML 6 however 
> the sequence is simply
>   1
> then abort is called and it sets readyState to 0.
> 
> MSXML 3 is what is installed with IE 6, the other MSXML versions are not 
> necessarily around to be used on the client.
> 
> 
> 
> 
this may help show the situation?
can see the comments in script area per version response.

<http://www.teamcon.com/pub/concepts/microsoft/msxml-xmlhttp-abortReadyStates.html>