It is impossible to set number with comma into input

By design Issue #6367416


Jan 29, 2016
This issue is public.
Reported by 5 people

Sign in to watch or report this issue.

Steps to reproduce


Repro Steps:

  1. Open the sample:
  2. Enter to input “15,6”
  3. After value change an input value is “”

Expected Results:

I expect that after number value with comma (e.g. “15,6”) is entered to input I will have correct value in it

Actual Results:

Dev Channel specific:



0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Amit J.”

      Changed Assigned To from “Amit J.” to “IE S.”

      Changed Status to “By design”

      Changed Assigned To from “IE S.” to “Grisha L.”

      Changed Status from “By design”

      Changed Status to “Confirmed”

      Changed Assigned To from “Grisha L.” to “IE S.”

      Changed Status from “Confirmed” to “By design”

    • Same problem here…

      I try use this code:

      var val = parseFloat($(this).val().replace(‘,’,’.’));

      But the "$(this).val()" return always “”

      On IE, chrome and firefox works fine - just in microsoft edge occurs this error!

      Change the input type for text is not a acceptable solution. For now I will continue recommend other browsers for my clients…

      Please, fix this!

    • Hello,

      Thank you for providing this information about the issue. An input element with attribute “type=number” can only accept dots and no commas. This convention follows localization system settings. The work around this issue is to use input element with “type=text” attribute value. This is common behavior across all major browsers.

      Best Wishes,

      The MS Edge Team

    • James M. Major browsers work fine you idiot, fix the issue you lazy bastard.

    • My app doesn’t work on edge “by design” too. It’s an awful solution to use type="text", my bindings fail, hard. Now, because one browser, I’ll have to deal with parse? Safari, Chrome, Firefox, Opera, UC Browser and others get it. Edge don’t. I’ve checked language, regional settings, and that doesn’t make any difference.

    • @James M.
      Given that your last post here is newer than the statement on – which was also marked as “by design” – and it states here that this issue per “convention” (aka not a bug but a feature), can we still expect progress on this?

      I was honestly surprised that something as general and elementary as number input types is unable to take the users localisation setting into account on Edge. Especially as any other major browser (Chrome, Firefox, Safari) performs this by default.

      This is especially bothersome, as our application itself uses Intl.NumberFormat in conformity to the Web Standard ECMA-402 (ECMAScript/Javascript Internationalization API Specification), wherefore all examples are provided according to the users localisation setting, but then Edge ignores internationalization for inputs.

      Given the history Edge comes from, this seems more to be something to expect from IEs bad legacy, than from a successor… and forces us in the end to recommend our users to avoid Edge because of this bug in particular :(

    • @James M.
      Other major browsers both parse the number with comma as a number, and stops me from inputting non-numeric characters in the numeric input field. Edge does not.

      From Microsoft’s design on number formatting, it seems the number 25,7 input on a german Edge should parse as a number.

      Please reconsider your singularly inconsistent design.

    • Commas are commonly use within numbers by normal users. Chrome, FF, Safari accept commas into number fields. An input as “text” for number input is a horrible solution, you have to remember there are normal people using these fields.

      This sort of behaviour causes a ton of code smell with all sort of special checks required on the front end.

    You need to sign in to your Microsoft account to add a comment.

    Sign in