Currently the spec says to fire an 'abort' event every time abort() is called, no matter what the current state is. This means that if you call abort() back to back five times you'll get five abort events.
This does match what Firefox does, however it seems to go against both logic and the ProgressEvent spec.
Is there a reason to not just fire the abort event when we are in fact aborting a network transfer?
Same thing applies partially to the abort event fired on the upload object. / Jonas
