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

@WebReflection 

> However in my initial design .cancel(why) was working as resolution for the promise

Well, because of the scoping of your cancel function (which looks weird but is great in practice), you have easy access to `resolve` and `reject`. Maybe, after the cancel callback is called, `reject(undefined)` is called automatically. That means the cancel callback *could* call `resolve`/`reject` itself. That means the creator of the promise could resolve with a partial value if that makes sense.

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