- From: ianbjacobs <notifications@github.com>
- Date: Mon, 07 Aug 2017 03:14:40 +0000 (UTC)
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 7 August 2017 03:15:01 UTC
ianbjacobs commented on this pull request. > @@ -841,9 +841,9 @@ </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. + <var>data</var> contains filters that exclude the payment I think Adrian's concern is the default behavior. Here's a version that endeavors to capture (what I believe is) the intent, but sticks closer to the language currently in the spec: <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 do not match those provided by <var>data</var>, the payment handler does not match, otherwise the payment handler matches.</li> For each resulting payment handler, if <var>data</var> contains filters that exclude the payment handler, then the payment handler does not match, otherwise the payment handler matches. -- 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/574#discussion_r131566058
Received on Monday, 7 August 2017 03:15:01 UTC