Re: [w3c/browser-payment-api] Currency Types and Rendering (#185)

@adamroach and @adrianhopebailie 

I like the direction of the evolving proposal:

 * The easy (standard) case remains easy (thanks to default value)
 * It gives extensibility for non-standard codes and increases the potential for interop
 * It does not require this WG to specify anything related to display
 * It does not require the browser to dereference any URLs. (The browser can just do string matching on an internal table.)



---
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/185#issuecomment-228124863