marcoscaceres commented on this pull request.
> + </li>
+ <li>Let <var>promise</var> be <a>a new promise</a>.
+ </li>
+ <li>Return <var>promise</var>, and perform the remaining
+ steps <a>in parallel</a>.
+ </li>
+ <li>For each <var>paymentMethod</var> tuple in
+ <var>request</var>.<a>[[\serializedMethodData]]</a>:
+ <ol>
+ <li>Let <var>identifier</var> be the first element in the
+ <var>paymentMethod</var> tuple.
+ </li>
+ <li>If <var>checkForInstruments</var> is false, resolve <var>
+ promise</var> with true and terminate this algorithm if either the
+ user agent has a <a>payment handler</a> that supports handling
+ payment requests for <var>identifier</var>, or if it can perform
I don't think we should mention the "just-in-time" stuff... that's a Chrome implementation detail that falls under "supports".
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-request/pull/833#pullrequestreview-204448232