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

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

--- Comment #15 from Mukilan Thiyagarajan <mukilanthiagarajan@gmail.com> ---
(In reply to Anne from comment #14)
> (In reply to Mukilan Thiyagarajan from comment #12)
> > Also, should Timeout and Network error events behave the same way as abort?
> > i.e if a timeout or network error happens while inside the readystate event
> > handler, should the subsequent "progress", "load", "loadend" events not be
> > triggered?
> 
> Timeout can only happen until the server has send back a response. The same
> is true for a network error.

I apologize, I should not have listed the "load" and "loadend" events. The
scenario I mentioned is possible when a "readystatechange" event is fired while
transitioning from "HEADERS_RECIEVED" to the "LOADING" state (as a part of the
'process response body'). While in the handler, the request is not complete yet
and could still timeout or result in an error. What happens in such cases?
Should the subsequent 'progress' event still be called?

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

Received on Monday, 20 October 2014 17:03:15 UTC