Make number's and <input>'s get along better #9172
Description
In the js world, numbers are dressed one way - the western way (which I'm quite thankful for). In the real world, people dress up numbers in all sorts of ways. I'm talking Intl.NumberFormat kinds of ways. When you want to go from a js number to an everybody number, easy! Just use Intl.NumberFormat. But when you want to go from an everybody number to a js number - good luck.
I understand the traditional solution has been to use <input type="text" /> and let the developers handle it, but most developers speak one or two languages, which makes the world wide web number-fractured. Numbers make the world go 'round. It would seem to me that everybody would benefit from an internationalized, flexible <input type="intl-numeric" /> or perhaps a more pure element like <number /> where users can enter the number according to their locale, developers have sensible handles to do developery things like specify the intent/styling of the number (like the second argument of Intl.NumberFormat) and dynamically delegate to their own parsers for implementing excel-like functionalities such as calculator.
This would be a massive undertaking, but in the end browsers would be able to intimately understand numbers from all people, languages, and relevant contexts. I would imagine this would amount to increased revenue for browser implementers once companies can easily support data entry on a international scale. The whole world speaks quantities - can browsers interpret?