- From: Benoit Girard <notifications@github.com>
- Date: Wed, 01 Nov 2017 05:18:09 +0000 (UTC)
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 1 November 2017 05:18:34 UTC
No it's orthogonal. But the problem in #1026 is a lot more urgent and impactful to fix. This issue mentioned here can be worked around by forcing a new service worker to install with skipWaiting which allows us to re-validate the cache or avoid registering the fetch handler to use the optimization from w3c/ServiceWorker#718. I had assumed this issue here would be a quick fix but devoting resources to #1026 is much more important. The reason they are orthogonal is image that the SW is being restarted and a preload request goes out. The server is generating markup but doesn't know the state that the SW is in so it cannot annotate tags with serviceworker="none" since the SW has not been started yet and hasn't communicated with the server yet by the time the page is being generated (assuming a slow SW startup and a high latency network with is typical). I don't think I did the best job at explaining the motivation for this issue. But this issue is sufficiently complex that I'm not sure what is miscommunicated here. A live discussion might be more effective so I'm happy to get on a call if anyone would like to discuss and get clarification on the issue. -- 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/1195#issuecomment-340981922
Received on Wednesday, 1 November 2017 05:18:34 UTC