[whatwg] Proposal for showing thousand separator in form controls.

[Михаил Гаврилов]

Hi to all!
Excuse me I am newbie here.
I want make a proposal for displaying thousand separator in numeric
input fields.
Most users would be more satisfied if in any  would seen as 1 234 567 890.012 345
678 9
of course thousand separator must depend of local settings.
1234567890.0123456789 = 1,234,567,890.012,345,678,9
Anyway thousand separator will not be sended to the server when the
form is submitted and not be accessed from Javascript for example:


console.log(document.getElementById('input1').value);
//return: 1234567890.0123456789

Ie thousand separator affects only the display of numbers for
improving readability.


--
Best Regards,
Mike Gavrilov.

Re: [whatwg] Proposal for showing thousand separator in form controls.

[Boris Zbarsky]

On 10/13/15 3:35 PM, Domenic Denicola wrote:

S ... any implementers interested in solving this problem?


Note that Gecko used to show such separators, then stopped doing that. 
See https://bugzilla.mozilla.org/show_bug.cgi?id=974175 for details.


It might be worth having some way to opt in to this sort of formatting, 
but the issues raised regarding editing in that bug report would still 
need to be sorted out...


-Boris

Re: [whatwg] Proposal for showing thousand separator in form controls.

[Jonas Sicking]

On Tue, Oct 13, 2015 at 12:35 PM, Domenic Denicola  wrote:
> especially since custom elements are unable to participate in the form 
> control ecosystem

That is very fixable though. There have been good proposals made.

/ Jonas

Re: [whatwg] Proposal for showing thousand separator in form controls.

[Domenic Denicola]

This has come up before; I think 
https://lists.w3.org/Archives/Public/public-whatwg-archive/2014Feb/0075.html is 
the most recent thread on the subject. In general, the spec does not mandate 
such UI features of browsers, but the input types are somewhat of a gray area 
in that regard, since part of their purpose is specifically to give better UI 
presentation.

My suggestion during that thread was to delegate to ES's i18n API: 
https://lists.w3.org/Archives/Public/public-whatwg-archive/2014Feb/0094.html

In general, this type of thing is hard to get support for these days. 
Implementers are more interested in getting stuff like web components in place 
so that authors can produce better controls, without waiting for them to be 
debated, standardized, and implemented everywhere. I think it'd be a worthwhile 
improvement, especially since custom elements are unable to participate in the 
form control ecosystem (constraint validation, form submission, etc.). But 
we're going to need implementer interest before anything gets done here.

S ... any implementers interested in solving this problem?