Thanks, Jenan. I updated the spec after today's call: https://w3c.github.io/webpayments-payment-apps-api/#payment-app-display The new text in 10.4 says: "To support scenarios that involve visual display and user interaction, user agents MUST allow payment apps to call the clients.openWindow() method defined in [SERVICE-WORKERS]. Because user agents can determine from event type that the window is part of a payment flow, the user agent SHOULD render the window in a way that is consistent with the flow and not confusing to the user. For example, we recommend that the payment app not be opened in a new browser tab, as this is too dissociated from the checkout context." How does that sound? Would you suggest we amend it to mention "full or partial frame" as a sort of good practice hint? Regarding origin: We do not currently have a requirement that the payment app must display its own origin to hte user. Do you think that should be a requirement or strong suggestion? Thanks! -- 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-273380883
Received on Wednesday, 18 January 2017 04:38:15 UTC