Re: [w3c/ServiceWorker] ready promise is kind of weird after you call unregister() (#1279)

Adding two cents: the lifecycle API's of SW are either too high-level or too low-level.

High-level APIs like `.ready()` fail to encapsulate edge cases like this
Low-level APIs become error prone to use (i.e. listening for state changes on a SW instead of a registration and checking for controller change events).

For the most part - this isn't an issue until you want to take advantage of `skipWaiting()` and `clients.claim()`.

-- 
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/1279#issuecomment-370511317