From 175fd98d07497b4059e341b76833d04306d71b31 Mon Sep 17 00:00:00 2001 From: Jake Archibald Date: Fri, 3 Nov 2017 13:58:38 +0000 Subject: [PATCH] Update explainer wording. Fixes #1111. --- explainer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/explainer.md b/explainer.md index 2db53672..80f24584 100644 --- a/explainer.md +++ b/explainer.md @@ -157,7 +157,7 @@ The lifecycle of a service worker is based on Chrome’s update model: do as muc Whenever you navigate to a page within scope of your service worker, the browser checks for updates in the background. If the script is byte-different, it’s considered to be a new version, and installed (note: only the script is checked, not external `importScripts`). However, the old version remains in control over pages until all tabs using it are gone (unless `.replace()` is called during install). Then the old version is garbage collected and the new version takes over. -This avoids the problem of two versions of a site running at the same time, in different tabs. Our current strategy for this is [“cross fingers, hope it doesn’t happen”](https://twitter.com/jaffathecake/status/502779501936652289). +This avoids the problem of two versions of a site running at the same time, in different tabs – something that happens by default on the web, and is the [source of really tricky bugs](https://twitter.com/jaffathecake/status/502779501936652289). Note: Updates obey the freshness headers of the worker script (such as `max-age`), unless the `max-age` is greater than 24 hours, in which case it is capped to 24 hours.