undecided → low
new → open
1.9.1 → 1.11.1
Looks like this has been around for a while. Aborting happens synchronously and cleans up the request to avoid memory bloat. Then when it gets back from the
ajaxSend it actually tries to send the request and the XHR object was blown out from under it.
Aborting the request doesn't make a lot of sense at that point, you can see from the XHR spec that it's pretty much a no-op if called before a
.send(). So it seems more appropriate to have
ajaxSend indicate that it doesn't want the request to proceed in some other way. The concern I'd have with making a change there would be compat. At least we know aborting doesn't currently work.
I'll mark this open for discussion.