[w3c/ServiceWorker] `updatefound` event in service worker context seems unreliable (#1255)

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 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?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1255