Re: [w3c/webpayments-payment-apps-api] Lambda functions for app matching (#76)

rsolomakhin commented on this pull request.



> +        <li>
+          Set <var>commonMethods</var> to the set union of
+          <var>paymentMethods</var> and <var>requestMethods</var>.
+        </li>
+        <li>
+          If <var>commonMethods</var> is a null set, this <a>payment app</a> is
+          not considered to be a candidate to handle the
+          <code>PaymentRequest</code> and terminate these steps.
+        </li>
+        <li>
+          If the <code>PaymentAppManifest</code> does not contain a
+          <code>canHandle</code> attribute, then this <a>payment app</a> is a
+          candidate for handling the <code>PaymentRequest</code>. Only those
+          <a>PaymentAppOption</a>s that have <code>enabledMethods</code>
+          containing at least one member of <var>commonMethods</var> are to be
+          displayed to the user. Terminate these steps.

Can we rephrase "to be displayed to the user" as "to be made available to the user for selection"? Chrome displays only one PaymentAppOption at first, with others available in a dropdown.

-- 
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/pull/76#pullrequestreview-12925808