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

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

--- Comment #12 from Mukilan Thiyagarajan <mukilanthiagarajan@gmail.com> ---
(In reply to Anne from comment #4)
> (In reply to Manish Goregaokar from comment #3)
> > For example, abort() can be called within an event handler (let's say
> > readystatechange at LOADING) -- should the progress event be fired as well?
> 
> Yeah, the idea was that would still dispatch. We could add more state to
> prevent this, but it does not seem worth it.

Chrome does prevent the triggering of the subsequent load and loadend events
when abort() is called from the readystatehandler (state = 4). However Firefox
does not exhibit this behaviour. 

Test page:
http://mukilan.github.io/servo_xhr_abort_prevents_progress_events.html


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?

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

Received on Monday, 20 October 2014 14:11:40 UTC