Re: [w3c/ServiceWorker] Handling duplicate importScripts() (#1041)

> So we will use the offlined version for the second importScripts().

> This makes sense to me, especially if Firefox is doing the same.

Thanks for the feedback.  What I like about this over "last one wins" behavior is that the resulting script before installation is the same as the resulting script after installation. I think it'd also be a tad easier for our implementation to not evict/overwrite the original cached script.

Also, I think for the recursive importScripts('main-script.js') case, I'll just read the cached script the same as any importScripts for an already-cached script. It'll still cause a stack overflow in Chrome.

-- 
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/1041#issuecomment-270647528