- From: Matt Falkenhagen <notifications@github.com>
- Date: Fri, 16 Dec 2016 00:11:56 -0800
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 16 December 2016 08:12:28 UTC
I think I know what's going on. Does the domain.com service worker have a fetch event handler? If not, then Chrome 54+ does not start it up for the navigation. This is an optimization, since the request will just go to network anyway. You can check this by finding the registration in chrome://serviceworker-internals and checking the field "Fetch handler existence". -- 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/1029#issuecomment-267540100
Received on Friday, 16 December 2016 08:12:28 UTC