- From: Jake Archibald <notifications@github.com>
- Date: Wed, 03 Aug 2016 09:34:03 -0700
- To: slightlyoff/ServiceWorker <ServiceWorker@noreply.github.com>
Received on Wednesday, 3 August 2016 17:02:28 UTC
If your SW is buggy, or something changes in a particular browser that causes it to start throwing errors, the user gets nothing until you fix your SW (unless the browser provides a "retry without service worker" feature). It'd be nice to allow the developer to recover in these cases In many cases, a `.catch()` at the end of the `respondWith` promise lets them do that, but not in the case of a response that fetch deems unacceptable, eg an opaque response to a CORS request. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/slightlyoff/ServiceWorker/issues/939
Received on Wednesday, 3 August 2016 17:02:28 UTC