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

> It feels like the spec should automatically resolve the ready promises of any matching clients whether the promise has been accessed or not.

I happen to have been working on https://github.com/w3c/ServiceWorker/pull/1277 from a day before this issue was filed.

It seems (1) still doesn't solve the multiple registrations case. Would it be impossible at all to make `.ready` attribute getter return a new promise when it detects a more specific-scoped registration?


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

Received on Wednesday, 14 February 2018 05:13:22 UTC