Re: [w3c/browser-payment-api] Should payment method specifications contain WebIDL? (#132)

> so why no use WebIDL?

Web IDL is unnecessarily restrictive. You can't extend dictionaries as you see fit and preserve the data from the caller of the API through to the Payment App. The payment specific data (not things that the user agent specifically calls out) is sent as an `object`. That includes the stuff defined in the BasicCardResponse, so there's no reason to use Web IDL and force its restrictions onto the data. Web IDL is only being used for the stuff that the browser manufacturers have indicated that they want broken out separately.

---
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/132#issuecomment-213024241