So, `PaymentRequestEvent.openClientWindow()` makes this window (client) special/built-for-purpose: binding it to the browser tab/window that initiated the PaymentRequest - and only allowing .openClientWindow() to be called once (it could just resolve with the same client), and for you to always receive, potentially, the same `client`. This means you can't spin up multiple overlays on a tab - you have to wait till it's closed before you can spin it up again. Also, because you know that it was a PaymentRequestEvent that initiated it, the browser can provide a more considered UX/UI if need be. But the main thing remains that you can only get one of these - irrespective of the number of service workers, etc... if someone claims this client, then they own it till they release it (somehow... we would need to work out those details). This frees the `ServiceWorkerGlobalScope.clients.openWindow()` clients to open normal browser tabs and continue to behave as they do today. -- 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/webpayments-payment-apps-api/issues/97#issuecomment-274749276
Received on Tuesday, 24 January 2017 09:17:07 UTC