Allow both locale specific and neutral decimal separator on the mobile keyboard to allow fractional numbers input to match Android

By design Issue #7315850

Details

Author
Asbjørn R.
Created
Apr 23, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
14.14328
Reports
Reported by 11 people

Sign in to watch or report this issue.

Steps to reproduce

Even if running a Danish build of Edge, <input type=number> fields only accept period as the decimal as decimal separator, not comma as used in most of the world outside the US and UK.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Rick J.”

      Changed Assigned To to “Bogdan B.”

      Changed Assigned To from “Bogdan B.” to “Kurt C.”

      Changed Status to “Confirmed”

    • Same for dutch build, return whitespace when trying to get value.

    • Same here! Brazil build always return a whitespace when I trying to get the values.

    • Is there an update about when this defect will be fixed and in which version?

    • Some feedback from Microsoft about this bug would be nice, PLEASE!

    • Microsoft Edge Team

      Changed Assigned To from “Kurt C.” to “Peter S.”

    • Same for Germany, please provide solution of work around

    • Same for French, this browser can’t be used for ecommerce managing html 5 type=number…

    • Microsoft Edge Team

      Changed Title from “<input type=number> does not support comma as decimal separator” to “<input type=number> does not support comma as decimal separator”

      Changed Title from “<input type=number> does not support comma as decimal separator” to “Allow both locale specific and neutral decimal separator on the mobile keyboard to allow fractional numbers input to match Android”

      Changed Status from “Confirmed”

      Changed Assigned To to “Jason W.”

      Changed Assigned To from “Jason W.” to “Jim W.”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed” to “Won’t fix”

    • Hello,

      Thank you for providing this information about the issue. Currently, we do not plan to release a fix for this problem. We are considering a solution for a future build.

      Best Wishes,
      The MS Edge Team

    • Microsoft Edge Team

      Changed Assigned To to “Jim W.”

      Changed Status from “Won’t fix”

      Changed Assigned To from “Jim W.” to “Benjamin P.”

      Changed Status to “Won’t fix”

    • Changed Status from “Won’t fix”

    • Excuse me?! So you’re being so arrogant that you only want to support US-style number formatting when the majority of the world uses commas for decimal places? And you wonder why people don’t use Edge?
      This is not only an issue on mobile, Edge simply return a blank value for the field when using a comma for decimals.

    • Hello,

      Thank you for all the feedback. We have received many requests to publish a fix for this problem, and we hear you all. We are working on this as a new feature (rather than a bug) and will provide an update once we have more information about when the solution will be available.

      Please do not lose hope if the status of this case becomes resolved or closed. I will personally continue to follow the solution and post the final news here.

      Best Wishes,
      The MS Edge Team

    • Microsoft Edge Team

      Changed Status to “By design”

    • @Dirk F. (Mar 12, 2017)
      It is incorrect, that only “.” is allowed by the HTML standard. As stated in section § 4.10.5.2 "Implementation notes regarding localization of form controls", the format shown to the user is independent of the format used for form submission.

      In particularly, the section states: “Browsers should use user interfaces that present locale-affected formats such as dates, times, and numbers according to the conventions of either the locale implied by the input element’s language or the user’s preferred locale. Using the page’s locale will ensure consistency with page-provided data.”

      It exists at least since the first recommendation of HTML 5 (28 October 2014) and is still valid in the most recent WHATWG and W3C HTML 5.3 version.

      While it is a non-normative section (as it is only a recommendation), Edge seems to be the only major browser (compared to Chrome, Firefox and Safari), that ignores/avoids it. However, I also do not know if Microsoft was generally in favour or against localisation at all (using their participation within the HTML standardisation process), especially since the localisation of number input types seems to be more of an elementary internationalisation feature.

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

    Sign in