Re: [w3c/ServiceWorker] Registering service workers for unique origins? (#1437)

URL.createObjectURL I think is generally considered a regrettable decision we wouldn't want to imitate.  As designed it encourages leaking resources, and as browsers need to implement it (at least Firefox), it's actually even more horrible under the hood.

Being able to register a single ServiceWorker on a special scope that's explicitly for opaque origins for this exact scenario might work, though.  Like: `navigator.serviceWorker.register("/script.js", { scope: navigator.serviceWorker.opaqueOrigins })` where the sentinel scope requires that it would have been legal to specify a scope of "/".

-- 
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/1437#issuecomment-503812165