I see this issue is on the agenda for today's meeting. I'm not sure if Rouslan's efforts have been fruitful, but I just want to make sure we consider the option of resurrecting the PaymentWindow API that existed in the very first versions of the service worker payment apps text. Although there's added spec complexity in defining this API, which necessarily needs to copy a lot of the spec text from clients.openWindow(), I believe it does address very well the current uncertainty w.r.t. the suitability of clients.openWindow(). It can also help us solve another problem which we haven't yet discussed, but which I have had feedback about from a payment app implementor; namely the difficulty of closing a window opened by clients.openWindow(). See [this](http://stackoverflow.com/questions/41352840/how-to-close-window-opened-by-serviceworker-using-clients-openwindow-in-chrome) and [this](http://stackoverflow.com/questions/19761241/window-close-and-self-close-do-not-close-the-window-in-chrome) stackoverflow post for more information. Basically, if a window has been opened by a serviceworker using clients.openWindow(), it may be tricky to close it again programmatically. If we have a specialized API for opening and closing payment windows, we can sidestep all of these potential problems. -- 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/73#issuecomment-273119925
Received on Tuesday, 17 January 2017 11:56:29 UTC