I’m trying to confirm if a Service Worker registration can disappear on Chrome under storage pressure and no Persistent Storage API call. It’s not simple to test; it’s clearer on the Cache Storage.
/cc @slightlylate @jaffathecake @cwilso
It's the same reason to have Cache Storage in the first place. The assumption behind the shared HTTP cache is totally different. That cache isn't "owned" by the app, so the app can't make assumptions about its state.
-
-
Because we can't know if your app will break if a rarely used CSS (or video or font) resource is gone, the Cache API makes it the developer's problem (because the developer understands what the app actually needs).
-
BTW, do you know what happens with a push subscription if a sw registration is removed by storage pressure? Is it marked as an expired suscription?
I’m thinking about the use case where you stop receiving push messages from a PWA and you don’t know why
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.