@adamroach I respectfully disagree. There is no mechanism today to wake up a service worker to perform a payment without spinning up a browser window. There is also no mechanism for the browser to spin up a "payment window/overlay" that is bound to the a browser tab. This API solves both those problems too. In the examples above show multiple ways of addressing the problem that continue to allow the API to function as intended while meeting the privacy requirements of not leaking data. -- 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/99#issuecomment-276272457
Received on Tuesday, 31 January 2017 04:30:52 UTC