I was hoping a new SW could be this kill switch (or even a fix switch), what's missing
-
-
-
you have to coordinate with your original code.
End of conversation
New conversation -
-
-
that is related to any cache system, local storage/IDB/whatever caching must have "forceUpdate"
-
your SW can do a background check for a change and force evict itself. That's a "kill switch"
-
browser already does it by looking for a new SW on each page visit. Why duplicate that?
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.