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

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

This matches what I plan to do in the implementation.  The tricky bit is that you also have to handle cleaning up the promises if they never settle and the client is detached/destroyed.  I have an implementation way to do that, but not sure about spec language.

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