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

F2F: We discussed some options:
* Add .ready to ServiceWorkerRegistration
* Add something like .getReadyPromise() alongside with .ready
There was agreement that if we were to do it over we'd have made .ready a function instead of a property. 

IMO: We should just add .getReadyPromise() [with a pithier name] and leave .ready semantics as they are instead of trying to improve it while stuck as a property. And if there are no actual problems this is causing in the wild, just don't change anything for now. 

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