W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2015

Re: [whatwg] Proposal for showing thousand separator in <input type="number " ... /> form controls.

From: Михаил Гаврилов <mikhail.v.gavrilov@gmail.com>
Date: Thu, 15 Oct 2015 18:58:48 +0500
Message-ID: <CABXGCsMY_gMr96j64c8gPrFSuwqZB4oihDTa5f8bnRYw5LsA1A@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: whatwg@lists.whatwg.org
I ran out of arguments.
I understand the proposal rejected?
Or maybe what any alternatives?
I understand an option to add an attribute to manually specify a
delimiter is not considered here. This option would allow in the case
when we display year, specify a empty delimeter for thousands.


1234

<input type = "number"  ... /> - use local settings for delimeter
1,234

<input type = "number" thousand = "" ... /> - use for removing
thousand delimiter
1234

<input type = "number" thousand = "-" ... /> - use for custom thousand delimiter
1-234


Maybe such variant will suit to all?




--
Best Regards,
Mike Gavrilov.


2015-10-15 18:45 GMT+05:00 Boris Zbarsky <bzbarsky@mit.edu>:
> On 10/15/15 2:35 AM, Михаил Гаврилов wrote:
>>
>> Let's first decide what numbers is meant by number type.
>
>
> Good luck with that.  Everyone seems to feel it's a different thing.
>
>> Also a special case is the number of a credit card and any number with
>> leading zero. Because leading zero no have significance and will
>> always be clipped in numbers. For such cases, it is necessary always
>> use text or masked text.
>
>
> And yet people consistently try to use <input type="number"> for these.  For
> credit card numbers it's silly, but for hours/minutes it's not unreasonable,
> if only to get the little up/down spinners.
>
> Yes, the fact that people are trying to shoehorn a wide variety of quite
> different use cases into <input type="number"> is unfortunate.
>
> -Boris
Received on Thursday, 15 October 2015 13:59:29 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:36 UTC