- From: Gray Zhang <notifications@github.com>
- Date: Mon, 02 Mar 2015 01:22:02 -0800
- To: slightlyoff/ServiceWorker <ServiceWorker@noreply.github.com>
Received on Monday, 2 March 2015 09:22:29 UTC
@tabatkins I'm afraid if in your code ```js var p = FetchPromise.resolve(waitForUserConfirm('press OK to continue')).then(() => fetch(url)); ``` the `p.abort()` can really abort the `fetch` process, which is a basic requirement for us, how can a `FetchPromise.resolve` create a `FetchPromise` which is aware of the `fetch` call? We don't need a `no-op` abort method, we need one which actually aborts the fetch --- Reply to this email directly or view it on GitHub: https://github.com/slightlyoff/ServiceWorker/issues/625#issuecomment-76680097
Received on Monday, 2 March 2015 09:22:29 UTC