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

>  its nice to be able to lazy create the .ready promise so we don't have to manage signaling activation to potentially every client open in the browser. Its doable, but its some memory/cpu overhead that it would be nice to avoid.

I agree we should avoid looking at potentially every client. Would it be possible to confine signaling activation to those clients that already lazy-created the `.ready` promise? In the spec, we might be able to initialize the `.ready` promise to null, set it to a promise when accessed, and make Activate look at those clients whose ready promise isn't null.

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