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

@NekR I'm honestly off philosophy because we have a real need and clock is ticking.

I've created 2 playgrounds few here keep ignoring: [one](https://gist.github.com/WebReflection/0ca8fac8013f76fb4d06) that cancels through reject and it ends up in the first catch instead of keep going as a cancel behavior I'd expect, and [one](https://gist.github.com/WebReflection/a015c9c02ff2482d327e) that silently resolves everything without executing a thing until the cancel and provides a way to resolve with arbitrary data from that point on. More convolute in terms of specs, but the best/surprise-free behavior I could imagine.

Both woudl work with async and await, as long as we consider async and await not finalized standards.
Otherwise it's pointless being here because everything, even controller, will fail with async and await row syntax.

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