You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Another issue @hiroshige-g explained to me is that service worker lifetime and version cycle is tied to the existence of clients. In particular, a service worker cannot upgrade to a new version while clients are alive.
Because we store the reserved client in the prefetch record, this means as long as there are any non-discarded prefetches, a site's service worker will not upgrade.
It'd be better if we allowed service worker upgrades, and evicted the associated prefetch records.
How exactly to specify this is not yet clear to me, as I haven't read up on how service worker lifetime and upgrades work. I worry that it might come down to https://w3c.github.io/ServiceWorker/#control-and-use which states
The rest of the section is non-normative.
The behavior in this section is not fully specified yet and will be specified in HTML Standard. The work is tracked by the issue and the pull request.
which links to a PR from 2017 that we never managed to land :(
The text was updated successfully, but these errors were encountered:
Another issue @hiroshige-g explained to me is that service worker lifetime and version cycle is tied to the existence of clients. In particular, a service worker cannot upgrade to a new version while clients are alive.
Because we store the reserved client in the prefetch record, this means as long as there are any non-discarded prefetches, a site's service worker will not upgrade.
It'd be better if we allowed service worker upgrades, and evicted the associated prefetch records.
How exactly to specify this is not yet clear to me, as I haven't read up on how service worker lifetime and upgrades work. I worry that it might come down to https://w3c.github.io/ServiceWorker/#control-and-use which states
which links to a PR from 2017 that we never managed to land :(
The text was updated successfully, but these errors were encountered: