Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9)

@adrianhopebailie,

> I think you're overstating the value this provides in this context which is why I'm also in favor of using a dictionary here and not an interface.

My understanding is that the algorithm used to copy a dictionary will cause any fields not specified in the Web IDL to be dropped. This sounds like a problem for extensibility. We may need a new Web IDL type that is "just data" but preserves unspecified fields.

---
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/9#issuecomment-200361535