- From: Vladan Djeric <notifications@github.com>
- Date: Thu, 05 Oct 2017 04:51:02 +0000 (UTC)
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 5 October 2017 04:51:29 UTC
Just to clarify some answers to your questions: > Are you seeing a delay on all fetches, or mainly navigations? We're seeing slow fetches of subresources (dozens of .js and .css files) through the do-nothing Fetcher during the initial load. I can look into whether do-nothing Fetches for resources loaded after initial page load are slow as well if you like. > When is Facebook looking to enable/disable the fetch? What are the conditions? Is it always before activate completes? We would disable fetches after client-side code notices the SW cache has become too old or when getting a signal from the server-side to invalidate the cache. This could happen in the activation event or it could be triggered by a main thread at some arbitrary point in time well after initial page load. -- 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-334358371
Received on Thursday, 5 October 2017 04:51:29 UTC