Re: [fetch] Aborting a fetch (#27)

@WebReflection, I'm starting to come around to the idea that cancellation has some sort of retroactive action.  I would still (rather strongly) prefer that this not be done without cooperation from the code that is being affected by this change.  That said, my objections have been addressed, at least from a technical standpoint.

I'm still totally against the idea that cancellation would manifest as success for several reasons.  If you have a long chain of fetches, you have no way of knowing which you are targetting with this, so rejection is the only way to ensure that you don't cause real problems.

Honestly, I never considered anything other than rejection as an option here.

I'm a little perplexed at the notion that you might somehow know to guard against cancellation.  If this is the right thing to do, then it should work uniformly and `Promise.resolve()` would be insufficient; though creating a new unresolved dependency might be OK, even if that dependency was a noop.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/27#issuecomment-87879135