Re: [w3c/ServiceWorker] Should a service worker be allowed to register new service workers? (#1117)

Just to chime in with some thoughts here: I have some experience using project-specific service workers on a site that also has a site-wide worker (some details [here](https://medium.com/the-guardian-mobile-innovation-lab/best-practices-for-using-notifications-and-service-workers-on-a-news-site-e90f01756c4d#7c5b)) and it would be incredibly useful for the two to be able to communicate, particularly given that they share the same storage allowance - the site-wide worker could tell old project workers to clean up storage/unregister them, etc. etc.

So, agreeing that it makes sense to limit `register()` for security reasons (though I'd like that too!), it would be great if we could still get the rest of `navigator.serviceWorker` in worker contexts, so that we can use `getRegistrations()`, then `postMessage()`, etc. etc. 

-- 
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/1117#issuecomment-320717095