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

> Also, it feels wrong to me that the spec kind of makes the result here depend on when the ready promise is accessed. It feels like the spec should automatically resolve the ready promises of any matching clients whether the promise has been accessed or not. That would provide the most predictable behavior.

Oh, I also thought about this a bit more.  I do actually like waiting for the first access to start this process.  I don't really want to send ready promise updates out to a bunch of clients that aren't even looking at them.

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

Received on Monday, 12 February 2018 14:59:27 UTC