[w3c/ServiceWorker] importScripts() on ServiceWorkerGlobalScope (#1319)

About `importScripts()` behavior called on various points of service workers, we'd had a long discussion in https://github.com/w3c/ServiceWorker/issues/1021. We didn't conclude that thread but found how browsers are implemented: https://github.com/w3c/ServiceWorker/issues/1021#issuecomment-266708110.

And the spec behavior hasn't changed since then. [The latest changes around importScripts()](https://github.com/w3c/ServiceWorker/commit/8e25c26efc932960a1449cf65de36dada371c867) just sorted out related issues on the byte-for-byte comparison matters. So, currently the spec flips the flag when the installation of a service worker version completes.

While discussing with my colleagues, I noticed Edge implemented the behavior conforms to the spec. And I checked out again that Chrome and Firefox don't throw when `importScripts()` is called in functional event tasks, but fetch the script from the network.

@mattto, @wanderview, I'd like to hear your thoughts on the implementation plan.

/cc @jakearchibald @slightlyoff @aliams @hober

-- 
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/1319