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

@benjamingr you are right, I think we failed in clear communication here. It has been almost a year, but we still want a solution that is good and fits well with the API. @domenic and @jakearchibald who are somewhat leading the charge here have ideas on how to solve this through cancelable promises. Development of that is taking a little longer due to other work taking priority, such as streams and `<script type=module>`, but we have not given up on pursuing that direction and will hopefully get to it soon.

Furthermore, if there are other issues on which you seek clarification, I think we'd be happy to blog more on blog.whatwg.org and elsewhere. It's not always clear to me personally what is clear and unclear to the rest of the world.

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