Use clients.claim() when available about ioweb2015 HOT 5 CLOSED

Would ServiceWorkerGlobalScope.skipWaiting() work for this use case? Making a non-animated page transition for a first view for all users will be a rather bad first impression, me thinks.

from ioweb2015.

skipWaiting() might help, but I'm not sure if skipWaiting() will cause the installing service worker to take control of the current page (as opposed to just activating it).

Once https://github.com/GoogleChrome/ioweb2015/pull/116/files is merged I'm going to play around a bit and see.

from ioweb2015.

I asked around a bit, and there's an additional method which isn't yet implemented called clients.claim() (see w3c/ServiceWorker#586) that will complement skipWaiting() and allow the active service worker to take control of all pages within scope immediately.

Once clients.claim() exists, this will all work the way we want. For the time being, we should consider the trade-offs. I don't feel too strongly about it, and mainly wanted to flag it as an edge case.

from ioweb2015.

It looks like clients.claim() will be around in the Chrome 42 timeframe. I'm fine with keeping things as-is for now and am keeping this open as a reminder to use clients.claim() once it's available.

from ioweb2015.

clients.claim() has made it into Chrome 43. Starting with sw-precache 1.2.6, it will be called when available. Since it's a patch version bump, it should get picked up automatically in our builds.

This means that under Chrome 43, the site will work offline as soon as it's loaded for the first time, with no reloads/navigations necessary.

from ioweb2015.