> What should the second .ready promise access do? The promise is not settled yet, but the previous access is in a parallel bit of algorithm waiting for '/bar' to activate. Should the second access block on that somehow or start waiting on '/bar/baz' instead? Honouring semantics, I would say it should start waiting on `/bar/baz` since that's the registration that controls the client and not the former one. Another alternative is to reject a second `.register()` intent after calling `.ready`. -- 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-369175454
Received on Wednesday, 28 February 2018 09:27:04 UTC