Chrome Version: 69.0.3497.81
Chrome OS Version: All
Chrome OS Platform: All
<b>Network info: <network, encryption type, router model (if known)></b>

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1) <input type="number" lang="pt" step="0.01" value="1.23" />
(2)
(3)

Expected Result:
Comma as decimal separator (eg: lang=pt) to final user, eg: default value = 1.23, should represent 1,23 on screen

Actual Result:
The value represented continue with dot as separator to final user, no matter the language.

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always

What is the impact to the user, and is there a workaround? If so, what is
it?
Final user gets confused. It generates a enormous problems for developers and business in whole world. We need to create a bunch of alternatives using complex and huge scripts to avoid this problem, because the number need to be represented with comma to final user, but behind (the code) need to be managed with dot (as default). This problems affects all platforms, including smartphones, tablets, etc. 

My suggestion, TO REDUCE IMPACT IN A SOLUTION:
 1) (instead "lang" tag) one suggestion is: use specific tags like "decimalSymbol=','" to represent comma or other symbol as decimal separator; decimal digits might be represented by a tag like "decimalDigits='3'" (to represent weights or others to final user, eg: '3.210' or '3,210' when decimalSeparator is comma), etc. The focus should be make use of input type "number" to final user type only numbers, nothing more is accepted, and the symbology behind should be set by developer (or use default).
 2) make input numbers works like https://gist.github.com/davidolesch/9961095 when setted tags currencySymbol, positiveFormat, negativeFormat, decimalSymbol, digitGroupSymbol, groupDigits, etc. The most interesting thing in this example, is that the final user never type dot or comma, they type only numbers and it's represented on screen as pre-setted format. The problem here is that input type need to be text instead of numeric, and behind (the code) the value is as the user see, needing to be converted back to default if something need to be calculated.




Please provide any additional information below. Attach a screen shot or
log if possible.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari: not tested
    Firefox: OK
    IE/Edge: not tested

See: https://www.w3.org/International/wiki/Locale-based_forms and https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/QpEoCwU0Ttg .