@jakearchibald, > And the window would have something like navigator.payments.provideResponse(response) which, when called, would close the window, and pass the result back to the service worker. Again, I'm in two minds about it, but it'd remove the need for the clunky postMessage work. This is almost exactly how the original API proposal from the Web Payments Community Group worked. The polyfill for it was implemented with `postMessage`, but the aim was to eliminate those clunky bits in the actual API as you've suggested. -- 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-274839287
Received on Tuesday, 24 January 2017 15:39:00 UTC