Good question. Rejecting seems fine. Alternately you could have some queue of to-be-shown payment requests, but I don't imagine anyone wants to implement that. Ideally there'd be some way to tell if this was going to reject before you called it, e.g. a `PaymentRequest.canShow` boolean or something. But that's not really necessary. Here's an important question: what is the scope of this? I think it should be either per browsing context or per top-level browsing context. (It could alternately be per user-agent, i.e. you cannot show a payment request while another tab is showing one. But that seems bad.) Basically, can iframes do a payment request while the parent document is doing one, or not? -- 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/462#issuecomment-288597174
Received on Thursday, 23 March 2017 02:15:47 UTC