I was so used to Visualforce fields that display a currency value in the
CurrencyIsoCode of the relevant record that it took me a while to understand why in Lightning wrong Iso Codes (those of the browser) are used.
- What is the recommended way to make Lightning currency fields behave like in the old times?
- Who cares abou the browsers currency if the value already has a database-stored semantic?
force:inputFieldrespect the CurrencyIsoCode and how can I make it work for generic (dynamic field name binding) usage?
- Which other Lightning component of the
ui:, namepace can and should be used with currencies and when?