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

those in ES6 with non cancelable promises will never be affected because those Promises won't be cancelable and, in the old logic, won't be canceled since nowhere the code will try to.

In case it does, those will be just silently resolved or forever pending so no code will ever be concretely affected.

As summary:

  * who use Promise today won't be affected
  * who'll use same code tomorrow also won't be able to interfere if that library does not expose cancelability
  * who need cancelability omorrow will expose it defining the how internally ... code that does nto care about it will always work anyway, code that needs cancelability won't

But the problem here is that we cannot "aside entirely Fetch" becaus it's specced as an API that returns a Promise.

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