Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870)

Okay, so the worry is about some kind of race condition if we match twice on the URL? I think you have mentioned that earlier.

The operations performed on client there don't make sense, right? Client doesn't exist yet for non-subresource requests.

I think here too it makes more sense if we end up dictating what service worker to use. Rather than letting "Handle Fetch" figure it out somehow and tell us about it later what it came up. 

It also seems plausible we might have more such cases in the future where you'd want to fetch something using a particular service worker.

One way to do this would be to change the "skip-service-worker flag" of request into a "service worker" setting. Which is one of "none", "client", or a service worker instance of sorts.

---
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/870#issuecomment-220301542