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

This makes no sense to me ... everyone using Fetch today will find suddenly a subclass which is cancelable which creates the exact scenario you say you want to avoid.

I never called that chaos bbecause I think Promise are already a mess anyway but we are going in circles here ... is Fetch API doomed forever? Accordingly with Kyle yes, I'd like to know it's not.

Thank you

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