- From: Bertrand Guay-Paquet <notifications@github.com>
- Date: Fri, 26 Aug 2022 14:37:21 -0700
- To: whatwg/xhr <xhr@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 26 August 2022 21:37:33 UTC
It seems that this step in "handle errors" is redundant: > 3. Otherwise, if xhr’s response’s aborted flag is set, run the request error steps for xhr, abort, and "AbortError" DOMException. A call to `abort()` unsets the `send() flag` via the "request error steps". This means that any future execution of "handle errors", before `open()` is called again, will immediately return: > 1. If xhr’s send() flag is unset, then return. Step 3 that checks the `aborted flag` will therefore never run, assuming the only way for the `aborted flag` to be set is to call `abort()`, Perhaps there is another way to set the `aborted flag` of an `XMLHttpRequest`'s response, but I couldn't spot it. Or is this unreachable step a way to future proof "handle errors" ? -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/xhr/issues/355 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/xhr/issues/355@github.com>
Received on Friday, 26 August 2022 21:37:33 UTC