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

@ianbjacobs said: 

> distinguish “how to display something” from “information necessary so that a user agent can make display decisions.”

This is splitting hairs. Call it what you will, our API doesn't fully support non-standard currencies unless we provide a way to help implementors displayed them properly to users so I wouldn't consider this low priority.

I don't consider a hard-coded short-list as support when there are hundreds of crypto-currencies in use today and new ones being invented all the time.

There are two ways we can do this:
1. Provide the browser with some help so it can display a currency identified by a URI using sane formatting
2. Strip away all of the functionality that requires the browser to display amounts so that this can be handled by the payment app. (i.e. The browser just shows an app selection dialogue)

I don't see the group agreeing to 2 and I don't think we have a good proposal for 1 yet.

---
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-222015036