- From: Matt Falkenhagen <notifications@github.com>
- Date: Sun, 04 Mar 2018 18:03:49 -0800
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 5 March 2018 02:04:16 UTC
Yes, Chrome's implementation tries to do what the spec and Firefox are doing, so it's an unexpected bug if it's doing something else. Could you file a bug if you can reproduce this? In Chrome's implementation, ServiceWorkerVersion (one service worker version) tracks its scripts in ServiceWorkerScriptCacheMap which maps a URL to a resource in the disk cache. The ServiceWorkerScriptCacheMap of one version shouldn't be sharing resources with the map of another version. You can see it gets populated by ServiceWorkerWriteToCacheJob, which always is given a new resource id for a given version + script url pair. -- 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-370289396
Received on Monday, 5 March 2018 02:04:16 UTC