Re: [w3c/ServiceWorker] [Feature request] Expose parent client ID for iframe navigations (#1556)

The root of the issue seems to be that you're using the same URL space multiple times and you're trying to use the transitive graph of client id's to differentiate them.  Can you elaborate more on why you need to reuse the same URLs?  What would it take to be able to assign each game it own URL space?

An important note is that the scope only matters for initial navigations of pages that are controlled by ServiceWorkers.  Once the ServiceWorker is controlling a page (whether by navigation or inheriting in the case of about:blank iframes), all of its subresource requests go to the ServiceWorker, even if they are notionally for resources that are hosted on other origins.  This can never be used to spoof the UI, but does allow some level of emulating resources stored on sub-domains, other origins, etc., other than the need to have an in-scope URL for the initial navigation.  (This may require use of `new Response(response.body, response)` in order to drop the URL field from any responses that actually did come from the network, however, in order for the controlled page's fetch to act like the response came from the Request URL).

I know previously in other issues you referenced problems with dealing with multiple versions of ServiceWorkers, is the choice in relation to that?  There has been work to allow changing the scopes of ServiceWorkers which might be of help with that. 

-- 
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/1556#issuecomment-748319193