Re: [w3c/ServiceWorker] Allow overlapping scopes (#1085)

Huh, actually it looks like with this setup, the `/r2/` SW caches the whole app but in Chrome that SW never handles any fetch events - they all get handled by the one at `/`. So in our case the `/` SW is magically able to serve the entire app because it happens to also be in the cache, but then the one at `/r2/` isn't handling fetch events, so we lose the ability to do extra features like lazy-caching responses.

Is this to spec? According to what @delapuente pointed out, shouldn't the fetch be handled by the SW with longest scope, i.e. at `/r2/`?

-- 
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/1085#issuecomment-290446688