[Bug 19470] Event firing sequence on abort() after send()

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

--- Comment #13 from Julian Aubourg <j@ubourg.net> ---
Just a small follow-up question so that everything is clear: what are the
fields of the xhr object like within those handlers that are executed after the
abort? No  more meaningful status, statusText and responseXXX fields? No more
headers from getResponseHeader()? Right?

It's an edge case but there is some kind of inconsistency in having the events
called with an xhr that isn't in the right state anymore / doesn't provide the
necessary information.

At the very least, the spec should make this abundantly clear because I don't
think many people would expect that.

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

Received on Wednesday, 20 February 2013 11:59:34 UTC