Re: [whatwg/xhr] Wrong state after abort() (#88)

Me too fine with fixing our implementation. Thanks for finding this berniegp.

> Maybe calling open() during abort() should not be supported, but if it is, the current behavior of Chrome leaves the request in a broken state. The user called open() but a subsequent call to setRequestHeader() would fail because the state is UNSENT.

Right. When only open() is called in onabort(), we enter UNSENT which is wrong. We'll address this too.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/xhr/issues/88#issuecomment-254761998