As a follow up to this morning's call: a new tab is not going to be sufficient for payment app implementors. I think the spec needs to be strong enough on this point to let payment apps feel confident that they can build an "Apple Pay on the Web"-like interaction (at the very least). That is, it needs to be capable of overlaying the current page. On mobile, new tabs have historically had some issues with certain UAs (e.g. SFSafariViewController does not work with tabs). Payment apps will want to be full frame and ideally be capable of building a partial-height UI with the host page visible in the background. On desktop, new tabs are a jarring user experience and force payment apps to render a full screen of UI even if all they want a small frame. As a payment app implementor, here is what I would need to feel comfortable building against this spec: - same window/tab - full frame or partial frame at my choosing, regardless of zoom/scroll position - indication of the origin of the payment app to the user Ex desktop:  Ex mobile:  -- 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-273369385
Received on Wednesday, 18 January 2017 02:59:23 UTC