- From: ianbjacobs <notifications@github.com>
- Date: Mon, 17 Apr 2017 16:18:01 -0700
- To: w3c/webpayments-payment-handler <webpayments-payment-handler@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/webpayments-payment-handler/pull/138/review/33112646@github.com>
ianbjacobs commented on this pull request. > the merchant with those supported by registered payment handlers. For payment methods that support additional filtering, merchant and payment handler capabilities are compared as part of determining whether there is a match. </li> - <li>The user agent displays matching payment handlers, displaying and - grouping Instruments according to information (labels and icons) - provided at registration or otherwise available from the Web app. + <li>The user agent displays a set of choices to the user. These choices + are <a data-lt="PaymentManager.instruments">instruments</a> that were + registered through the <a>PaymentManager</a> of candidate payment + handlers, displaying and grouping the choices according to information + (labels and icons) provided at registration or otherwise available from + the Web app. </li> Proposed simplification: <li>The user agent displays a set of choices to the user: the registered <a data-lt="PaymentManager.instruments">instruments</a> of candidate payment handlers. The user agent displays and groups these choices according to information (labels and icons) provided at registration or otherwise available from the Web app.</li> -- 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-handler/pull/138#pullrequestreview-33112646
Received on Monday, 17 April 2017 23:18:58 UTC