Strange refresh behavior

[boozedog]

Thanks for the very cool proof of concept!

I am running into one strange behavior on https://richardanaya.github.io/wasm-service/

If I hold shift+refresh on this page then the service worker stops intercepting the network calls and I start getting a bunch of HTTP 405 (Method Not Allowed) errors.

To get it working again, I just have to hit refresh (without the shift key pressed).

Tested in a couple different Chromium-based browsers.

Please let me know if there's any other information I can provide!

[infogulch]

Yes I've also noticed this, but I'm not sure exactly what to do about it. It could probably be fixed by using some particular api in a certain way, but I wasn't able to discover the correct usage.

See my notes on #5

The ServiceWorker eventually stops intercepting requests and I don't know why. This may be an error in the code, but I cleaned it up as much as possible and added logging for all relevant events and don't see any indication in code when the SW is unloaded, and it doesn't start back up automatically.

I suspect the issue is the implementation, but I have not found the culprit by combing through examples and MDN docs.

[boozedog]

@infogulch I was able to get this resolved thusly:

navigator.serviceWorker
  .register("./sw.js")
  .then((reg) => {
    console.log("SW registered!", reg);
    if (!navigator.serviceWorker.controller) location.reload();
  })
  .catch((err) => console.log("Boo!", err));

(a little hacky)