Skip to content
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

updatefound event in service worker context seems unreliable #1255

Open
wanderview opened this issue Dec 22, 2017 · 0 comments
Open

updatefound event in service worker context seems unreliable #1255

wanderview opened this issue Dec 22, 2017 · 0 comments

Comments

@wanderview
Copy link
Member

wanderview commented Dec 22, 2017

Currently we expose the service workers current registration as self.registration. In theory, the service worker can add an updatefound event handle on the registration to know when an event happens. This event in a service context, though, seems unreliable since it doesn't use ExtendableEvent. For example:

  1. The updatefound event does not start the service worker if its been stopped. (AFAICT)
  2. The updatefound event does not provide an event.waitUntil() method.

Should updatefound be usable in a service worker context? If so, should the browser start the worker to fire this event and should it be an ExtendableEvent? If its an ExtendableEvent, should waitUntil() delay the installation of the update?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant