- From: Rouslan Solomakhin <notifications@github.com>
- Date: Wed, 28 Feb 2018 07:02:35 -0800
- To: w3c/payment-handler <payment-handler@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/payment-handler/issues/250/369266816@github.com>
@stpeter: > With respect to skipping the sheet if there is "a single payment method name", are those the old payment method identifiers ("visa", "mastercard", etc.) or the new PMIs (e.g., "basic-card"). Neither. It's URL-based payment method identifiers, such as `"https://google.com/pay"`. > With respect to skipping the sheet if there is a "URL-based payment method name", does that mean (a) there is only a single PMI and it is a URL-based PMI, or (b) the list of PMIs includes a URL-based PMI? It's a single PMI and it's URL-based. > As to your "interesting point", do you envision that the precedence order is one-way (i.e., the browser is in control but can cede control to the payment app under certain conditions) and therefore that the user's browser preferences take precedence over the user's per-app preferences? Correct. The browser is in control. The payment app can decide whether to open its own HTML page via `PaymentRequestEvent.openWindow(url)`, but it cannot direct the browser to skip the payment sheet. > the browser would need to [...] potentially also adjudicate among competing "claims" from multiple payment apps Chrome does not skip the payment sheet if multiple payment apps are installed for the PMI. Then the user would be given the choice of payment apps in the browser payment sheet in every PaymentRequest. -- 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/payment-handler/issues/250#issuecomment-369266816
Received on Wednesday, 28 February 2018 15:04:40 UTC