Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33)

Another way to address this is to copy the pattern employed by getUserMedia() for constraints (which are passed as a dictionary): we could define a dictionary (e.g. `PaymentOptionsSupportedUserData`) that contains a key for each kind of data that is supported by the browser implementation. See [`MediaDevices.getSupportedConstraints()`](https://www.w3.org/TR/mediacapture-streams/#mediadevices-interface-extensions) and [`MediaTrackSupportedConstraints`](https://www.w3.org/TR/mediacapture-streams/#media-track-supported-constraints) for an example of how this works.

---
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/33#issuecomment-227291454