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

yes @jan-ivar the only thing needed was a special case/override of the returned object with a `.cancel` or `.abort` method because the problem was: "how to stop a request at all before the response is ready?"

It could have been a 10 minutes task as generic library PR/fix and yet, after a year, there's no way to do that because the solution should be universal.

I, myself, changed my mind about Promises and realized they are just perfect for what they do and I don't care about their cancellability, what I care about is chosing Promise when Promise is the best choice for whatever new API will go out in the future.

In this fetch case, returning directly something un-cancelable, Promise wasn't simply the best choice and the fact in over a year we are still discussing how and where and if fully demonstrated it.

I hope these mistakes won't be repeated in the future, for now long live to libarries able to fix this ... as long as these are libraries and **not** polyfills.

Polyfills are about standards, bringing an `.abort` in has nothing to do with following the polyfill approach.

Best Regards

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