[w3c/browser-payment-api] Matching algo doesn't handle (#532)

The following text does not handle the case where the filters provided by `data` are empty and the capabilities supplied by the payment handler are not. This should result in a match (i.e. No handlers are filtered out)

The WG sought to alleviate confusion around this topic by using the term "capabilities" to indicate the properties of the payment handler considered in this algorithm and the term "filters" to indicate the parts of the payment method specific data considered in this algorithm.

This has been excluded from the current text:

```html
<li>Determine which <a>payment handlers</a> support any of the
  <a>payment method identifiers</a> given <var>identifiers</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>
```

Proposed amendment:

```html
<li>Determine which <a>payment handlers</a> support any of the
  <a>payment method identifiers</a> given <var>identifiers</var>.
  For each resulting payment handler, if <var>data</var> contains
  filters that exclude the payment handler on the basis of the 
  capabilities it has supplied, then the payment handler
  does not match, otherwise the payment handler matches.
</li>
```


-- 
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/issues/532