[Bug 27033] XHR request termination doesn't terminate queued tasks

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27033

Mukilan Thiyagarajan <mukilanthiagarajan@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mukilanthiagarajan@gmail.co
                   |                            |m

--- Comment #11 from Mukilan Thiyagarajan <mukilanthiagarajan@gmail.com> ---
> It may be noteworthy that implementations consistently let open() prevent
> the abort processing's onloadend event from firing. AFAIK the spec is out of
> tune with implementations here.

I'm seeing the opposite behaviour on both Firefox (32.0) and Chrome
(38.0.2125.104). Here is a test page that demonstrates the issue:

http://mukilan.github.io/servo_xhr_abort_and_open.html

In this test case, open is called from the onabort event handler and yet the
loadend event is fired. Chrome does not even terminate the processing of the
state change event from 2 to 3 (LOADING) from where we invoke abort(), and
proceeds to fire the 'progress' event associated with the state change to
'LOADING', after the request has been aborted.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 20 October 2014 13:19:03 UTC