- From: Marcos Cáceres <notifications@github.com>
- Date: Thu, 10 Aug 2017 00:26:33 +0000 (UTC)
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 10 August 2017 00:26:57 UTC
marcoscaceres commented on this pull request. > @@ -839,33 +841,33 @@ <var>acceptPromise</var> with that error and terminate this algorithm. </li> - <li>Determine which <a>payment handlers</a> support - <var>identifier</var>. For each resulting payment handler, if - payment method specific capabilities supplied by the payment - handler match those provided by <var>data</var>, the payment - handler matches. + <li>Add each <a>payment handler</a> that supports We discussed this on today's Editor's call. @zkoch gave me a "reality check": when Chrome does work in concert with third-party payment methods (native apps in this case), they do "fail fast" at this point. Given that what I sought was confirmation that another use agent was in fact doing doing the filtering, then I concur and will add the text that @ianbjacobs suggested. -- 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-request/pull/578#discussion_r132339816
Received on Thursday, 10 August 2017 00:26:57 UTC