Re: [w3c/browser-payment-api] Currency amount (#101)

@zkoch the PR addresses the inconsistency between the spec and the resolution made by the group not just in the naming but also the fact that we resolved to use unsigned numbers and allow any string as a currency identifier. See w3c/webpayments#57

On that basis the PR is non-controversial and should be merged. However, if there is a desire by the group to revisit that resolution then let's do that once the spec is at least consistent with the WG consensus as previously recorded.

@kirkalx The browser API is not the place to enforce validation against a) a list we don't control and b) a list that does not include all of the values we know we want to support. I'd be very concerned if we expected user agents to do data validation on this beyond very basic format conformance.

The set of supported currencies SHOULD be defined per payment method so we should leave it for the payment method specifications to restrict the currencies they support if they wish to do so.

This will then be validated by the payment app that processes the payment request.

---
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/pull/101#issuecomment-204317765