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

Sure. I'd like to hear more from implementers about feasibility. Here's my thought on @mattto's comments.

> We have to cache .ready in each context and then alert each context when there was a change (unregister or a new register took effect)

I think we're already maintaining .ready for each context. Yes, alerting each context from unregister and Activate would have to be added. We're already doing similar signaling for `statechange` events and `controllerchange` events.

> , and that alert might or might not reach the context before .ready resolves again.

AFAICT, the matching service worker registration calls initiated from `.ready` and from Activate would scheduled in the same thread. So either task would set the ready promise to a new promise that resolves with a more specific-scoped registration only when needed.

/cc @wanderview @aliams @cdumez

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