Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)

I think its discouraged to change a property that returns a promise.  It would be more conventional if it was a function.

The other part of the spec that I don't think browsers implement is the bit about locking in the registration and waiting for it to activate in step 3 here:

https://w3c.github.io/ServiceWorker/#navigator-service-worker-ready

The implication of the current spec text is that you can get a registration with a `.installing` worker, but not active yet and start waiting.  If the registration fails to install and goes away, though, you are stuck with ready pointing at this dead registration.

I don't think browsers do this.  I think at least firefox and chrome probably wait for the first registration that gets a `.active` worker.  I need to write a test for this.

-- 
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/1278#issuecomment-365628969