- From: Domenic Denicola <notifications@github.com>
- Date: Fri, 06 Apr 2018 14:24:10 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 6 April 2018 21:24:32 UTC
Hmm, very interesting. It looks like it would be OK to set these to null for create a classic/module script, and have you patch them up later. We just need to fix the HTML algorithms to support null. I can do that. But first I am concerned about another thing... The fetch a module worker script graph algorithm seems to depend on the module map settings object for other purposes, for example, preventing multiple concurrent fetches of the same URL. I am worried about how that would be implemented given that the realm is not yet created. This is similar to what I said in https://github.com/w3c/ServiceWorker/issues/1013#issuecomment-287208088: > I'd be very surprised if any implementation actually parses service worker scripts before creating an instance of the JS engine for the service worker scripts to run in. And the spec should ideally not do something so different from implementations. Maybe implementers can comment on how they implement service worker script parsing and realm initialization? -- 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/pull/1294#issuecomment-379385057
Received on Friday, 6 April 2018 21:24:32 UTC