[whatwg] [XHR] changes in abort() steps

Anne van Kesteren annevk at annevk.nl
Fri Sep 13 01:35:40 PDT 2013

On Fri, Sep 13, 2013 at 6:42 AM, Jungkee Song <jungkee.song at samsung.com> wrote:
> In the recent change in abort() steps, is it intended to NOT change the
> state to UNSENT for an ongoing (the send() flag set) request? It's observed
> that Chrome, Firefox, IE all set it to UNSENT. Also, a few test cases in W3C
> tests have assertions on it:
> request.send();
> request.abort();
> request.assert_true(client.readyState, [0]);

Good catch! I totally missed abort() would always end up in UNSENT.
Tried to make that clearer by appending " first" to "Otherwise, run
these substeps".


More information about the whatwg mailing list