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

@ianbjacobs,

We are missing each other here. You are quoting only parts of what I am saying and those statements are being interpreted out of context.

* I AM NOT advocating that we MUST use URLs nor am I making any assertions about what a URL should point at if we do.
* I AM NOT saying _"we must specify how to display non-standard currencies"_
* I AM saying that we need to define a way for someone who mints a new currency identifier (i.e. non-standard) to also be able to _provide **display guidance** to a user agent_.

> We are not specifying any display behavior for any currency, however that currency is identified (ISO Code or otherwise).

Correct. But, as I have already said, user agents already have guidelines about how to display standard currencies so providing display hints is not required for these. If we don't provide a way for developers to pass display guidance to the browser for non-standard currencies then how will browsers ever do this consistently?

In triaging this issue I looked at what has been said to date and my conclusion was:

> I don't think we can leave this with __no hints for the browser__ about how to display non-standard currencies. I am 👎 to what's been proposed so far until we can address that.

Nothing anyone has said since, has proposed a way to:

1. provide display hints to the browser for non-standard currencies OR
2. drop support entirely for non-standard currencies OR
3. alter the API so that the browser never has to display amounts (and therefor currencies)

so my conclusion in evaluating this issue is that it still requires further proposals.

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