Re: [w3c/ServiceWorker] Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (#1195)

> I had assumed this issue here would be a quick fix but devoting resources to #1026 is much more important.

In some ways implementing #1026 is much easier to implement.  At least in gecko we have a flag we can add to network requests to bypass service worker logic completely.  I imagine other browsers must have something similar given current features.  Implementing #1026 would simply be exposing an API to add that existing flag.

> This issue mentioned here can be worked around by forcing a new service worker to install with skipWaiting which allows us to re-validate the cache or avoid registering the fetch handler to use the optimization from w3c/ServiceWorker#718. 

Honestly this doesn't seem like a bad way to solve the problem to me.  I like that it uses our stateful versioning based on SW script identity.

> A live discussion might be more effective so I'm happy to get on a call if anyone would like to discuss and get clarification on the issue.

TPAC is next week.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1195#issuecomment-341115238