-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
serviceworker.skipWaiting #1016
Comments
F2F: lukewarm reception. If it's trivial, we can do it. "If it can live on the main window, it should". |
Taking it one step further, it would be nice to be able to, from the active worker, call
Use case: a worker decides it's not in a good state and wants to force upgrade to the latest. EDIT: I think the proposal of |
According to #1303 (comment) linkedin wants this. |
Allowing:
Usecase: The new service worker has installed, I've shown a message to the user like "New version found. Update now?", which they have clicked.
Currently developers have to
postMessage
to the service worker for this behaviour.It's also an opportunity for us to rethink when
skipWaiting
should resolve in this case. It could resolve once the service worker has begunactivating
.The text was updated successfully, but these errors were encountered: