Custom Properties: Unable to correctly save decimals with german browser locale

Overview:
On folio-testing and snapshot, it is not possible to correctly save a deicmal values for custom properties. It seems that this is related to the german browser locale.

(In FF, there are also fields turning red while validating, but they are saved anyway. In addition ",0" behaves differently to Chrome. But as FF is not officially supported, you can ignore that. All behaviour described below is Chrome.)

Steps to Reproduce:

1. Create an agreements custom property with a decimal value.

A. German-German

1. Set Chrome browser locale to German
2. Set Folio session locale to German
3. Go to an agreement, edit the test custom property (see below)

B. German-English US

1. Set Chrome browser locale to German
2. Set Folio session locale to English US
3. Go to an agreement, edit the test custom property (see below)

Actual Results:

A. German-German

• 16.4 -> 164
• 16.0 -> 160
• 16,4 -> 164
• 16,0 -> 160

B. German-English US

• 16.4 -> 164
• 16.0 -> 160
• 16,4 -> 164
• 16,0 -> 160

Expected Results:

Most importantly, all behaviour regarding . vs, as separator should be consistent across Folio.
That said, my intuition as a German user would be as following:

• 16.4 -> validation error, wrong separator
• 16.0 -> validation error, wrong separator
• 16,4 -> 16,4
• 16,0 -> 16,0 or 16

Additional Information:

In Germany, the dot is indeed used as a reading aid separator, setting apart 3 digit groups for large numers, e.g. 1.000.000,00. It's the same as in the English version, only vice-versa.
When entering a number, we would most likely never write this dot, it's neither saved in a database nor entered, only displayed (sometimes).

Interested parties: Non-english users, esp. Germans.