> However, would this be a problem for scenarios where users only interact on origin A -- which uses postMessage to trigger origin B (in an iframe) to call the API? Are there existing payment systems that look like this or that may want to function this way if adopting the payment request API? User agents can propagate the user gesture across the postMessage boundary. WebKit does this today, for example. I would expect some implementors to want to make `show()` conditional on a user gesture, so that definitely shouldn't be prohibited by the spec. I don't know if it needs to be required. -- 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/browser-payment-api/issues/486#issuecomment-290218972
Received on Wednesday, 29 March 2017 20:41:54 UTC