Assume there is a Field aaaNumber__c on Account defined as Number(12,2)
Now I use it like this
<aura:component controller="elfL1" implements="forceCommunity:availableForAllPageTypes,force:appHostable">
<aura:handler name="init" value="{!this}" action="{!c.init}"/>
<aura:attribute name="account" type="Account" default="{ sobjectType: 'Account' }" />
<h1>Test1</h1>
<form>
<force:inputField value="{!v.account.Name}" class="form-control uiInput--input input" />
<force:inputField value="{!v.account.aaaNumber__c}" />
<br /><br /><br /><br /><br />
<ui:button class="form-control" aura:id="button" label="Save" press="{!c.save}"/>
<br />
</form>
</aura:component>
My locale is set to "German (Germany,Euro)", this means the decimal separator is a comma , not the English dot . - this is very consistent along the aloha UI and Visualforce, too.
Now on the Lightning Component, when I enter a number I can write something like 20,3 and it will be saved correctly... BUT after reloading the page, it turns into 20.3 - with the dot.
How can we ensure that the locale is respected consistently in Lightning?
As you see, this runs in a Community created by Lightning Community Builder.
Client- and serverside controllers are like here - only querying aaaNumber__c additionally.
Alternatively I've tried to fall back to
<ui:inputNumber class="form-control" value="{!v.account.aaaNumber__c}" />
instead of
<force:inputField value="{!v.account.aaaNumber__c}" />
but the result is exactly the same.
UPDATE:
It's even worse. As described above if you save 21,3 it turns to 21.3 - now if you reload the page and get 21.3 and change this again to 21.33 and save again an reload, you get 2133 - without any decimal point at all.
Either I'm doing something wrong or this is a serious bug.
