[w3c/browser-payment-api] supportedMethods (URL and enums) (#464)

The spec currently specifies: 

```
dictionary PaymentMethodData {
    required sequence<DOMString> supportedMethods;
};
```

But those are not actually strings: they are either enums (e.g., "basic-card") or USVStrings for URLs. This causes problems when doing URL comparisons as required by the Payment Method Identifiers spec (which calls into the URL spec).  

-- 
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/464