marcoscaceres requested changes on this pull request.
> @@ -147,6 +147,10 @@
<li>Allow the user agent to act as intermediary between merchants,
users, and <a>payment method</a> providers.
</li>
+ <li>Enable user agents to streamline the users's payment experience
nit: s/users's/users'
> @@ -2702,12 +2701,12 @@
A page might try to call the payment request API repeatedly with only
one payment method identifier to try to determine what payment
methods a <a>user agent</a> has installed. There may be legitimate
- scenarios for calling repeatedly (for example, to control the order
- of payment method selection). The fact that a successful match to a
- payment method causes a user interface to be displayed mitigates the
- disclosure risk. Implementations may also require a user action to
- initiate a payment request or they may choose to rate limit the calls
- to the API to prevent too many repeated calls.
+ scenarios for calling repeatedly (for example, to control the
+ sequence of payment method selection). The fact that a successful
"sequence" is problematic, because there is already WebIDL sequence defined.
--
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/browser-payment-api/pull/506#pullrequestreview-34998261