[w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305)

How realistic is it that anyone will support any currency system other than ISO4217? 

It seems like a recipe for disaster if UAs start supporting anything but one. 

Furthermore, if the UA supports more than one, then how can the developer check what currency systems are supported by the UA (apart from forcing an exception). 

In fact, the "currencySystem" is not used anywhere in the algorithms, so IMO it should be dropped entirely from the API: the spec should just say "The currency system is X" and the currency values then represented by an WebIDL enum.  


-- 
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/305