Use skipWaiting(), and prompt for refresh (not force-refresh) on SW update about ioweb2015 HOT 4 CLOSED

+1 That would be just awesome

from ioweb2015.

I got some confirmation that skipWaiting() will ship with M41. If we start using it, we can prompt users to perform a regular reload (instead of a force-reload) and know that the new content will be used, even if there are other tabs open that are using the old service worker.

So it's probably a good idea to start using it. We're not going to be able to ditch the toast entirely—which does makes sense, since the page is already rendered at the point the message appears, and we're telling the user that they have to take some action to see the updated page.

I've assigned this to myself to track adding in skipWaiting() to the sw-precache codebase, and changing the toast message. Also, we could actually perform the reload when you tap on the toast.

from ioweb2015.

Jeff on staging I see the toast always show up on page load. Is that
intended?
On Jan 8, 2015 9:22 PM, "Jeffrey Posnick" [email protected] wrote:

I got some confirmation that skipWaiting() will ship with M41. If we
start using it, we can prompt users to perform a regular reload (instead of
a force-reload) and know that the new content will be used, even if there
are other tabs open that are using the old service worker.

So it's probably a good idea to start using it. We're not going to be able
to ditch the toast entirely—which does makes sense, since the page is
already rendered at the point the message appears, and we're telling the
user that they have to take some action to see the updated page.

I've assigned this to myself to track adding in skipWaiting() to the
sw-precache codebase, and changing the toast message. Also, we could
actually perform the reload when you tap on the toast.

—
Reply to this email directly or view it on GitHub
#100 (comment)
.

from ioweb2015.

What's deployed on staging right now registers the old sw.js, and the code in that file is erroring out before completion, leading to the SW never properly registering. Each time the page loads, a new "Installing..." toast appears because the page tries (and fails) to register sw.js again.

It shouldn't be an issue with the new service-worker.js code that is auto-generated and includes the precaching logic.

from ioweb2015.