Localization of input type number

JavascriptHtmlLocalization

Javascript Problem Overview


I work on a web application running in Chrome, where I have inputs with type number. In my locale commas are used for decimal numbers and a space is used for thousand separation (not that important), but when I enter these characters into a number field, they are simply removed, effectively increasing money amounts by a hundred.

I have set the language both in the browser settings and on the page, but I still need to use a period for decimals. Is there any way I can configure the field to accept commas?

Alternatively, I'll have to solve this using javascript. I guess I could handle the keydown event and change commas to periods as the user types, but that wouldn't give a great user experience, would it? So how can I acheive this with a minimal footprint in my code?

Javascript Solutions


Solution 1 - Javascript

The HTML5 input type=number is inadequate from the localization point of view, due to both the definition and the implementations. It is meant to be localized but as per the locale of the browser, which you cannot set or even know as a designer/author.

On my Chrome, the input type=number step=0.001 accepts 1,2 (with comma) and sends it as 1.2 and it accepts 1.200 (with a period), visibly converting it to 1200 and sending as such. This is how things are meant to be, more or less, when the browser locale is Finnish. But it fails to accept 1 200 (which is standard way of writing 1200 in Finnish) and instead sends just the digit 1.

So it’s rather hopeless. Use whatever JavaScript widgets you can find, or a simple text input box. Anything is probably better than input type=number unless all users use browsers with the same locale and have the same expectations on the format of numbers.

Solution 2 - Javascript

If you don't need the up/down ticks, than follow workaround can help:

for comma (,) only (like german syntax):

<input type="text" pattern="[0-9]+([,][0-9]{1,2})?" name="amount">

dot (.) only:

<input type="text" pattern="[0-9]+([\.][0-9]{1,2})?" name="amount">

both but don't together: (no 1000 seperator)

<input type="text" pattern="[0-9]+([\.|,][0-9]{1,2})?" name="amount">

otherwise number for German/Deutsch:

<input name="myinput" value="0" step="0.01" lang="de-DE" type="number">

and style it with:

input[type=number] {
    -moz-appearance:textfield;
    -webkit-appearance: none;
    appearance: textfield;
}

Also lang "global" attribute can change behavior (thx @florian) of all input elements without own lang attribute:

<html lang="en">

See:

List of valid lang values: https://github.com/libyal/libfwnt/wiki/Language-Code-identifiers

Solution 3 - Javascript

The spec is clear: only a period is allowed as the decimal separator. Its up to the browsers to provide localization support for forms. Thousand separators are not allowed.

Solution 4 - Javascript

Unfortunately these characters are not allowed in the <input type="number">

See the specs here : http://w3c.github.io/html-reference/datatypes.html#common.data.float-def

Is this the format you want ? http://jsfiddle.net/S8rqY/

Solution 5 - Javascript

While Chrome uses the Browser setting, Firefox doesn't. At least not always - e.g. when there is a lang attribute in the <html> tag, Firefox uses this.

However, you can pass the lang attribute also to the <input> tag directly. Combining this with the Navigator API can simulate Chromes Behaviour.

Minimum example in React:

<input
  type="number"
  lang={navigator.language}
/>

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionJ&#248;rgenView Question on Stackoverflow
Solution 1 - JavascriptJukka K. KorpelaView Answer on Stackoverflow
Solution 2 - JavascriptFrankView Answer on Stackoverflow
Solution 3 - JavascriptDanielView Answer on Stackoverflow
Solution 4 - JavascriptwakookaView Answer on Stackoverflow
Solution 5 - JavascriptBenedikt BöhmView Answer on Stackoverflow