4 ms·
Thanks for this. Agree it depends on the context. And we like boring too ^_^ In our case, it's an optional / configurable preference, so I think we check that
by herodoturtle 4y ago
Thanks for this. Agree it depends on the context. And we like boring too ^_^
In our case, it's an optional / configurable preference, so I think we check that box.
Put another way, this isn't a blanket policy applied to all numeric input fields. Instead it's just for one particular input field, where large numbers are entered.
Now we don't want the users to have to enter the thousands separator manually (and besides, the raw integer is ultimately what is stored too).
So what we've currently got is the input field, with the formatted preview adjacent to it, kinda like so:
[123456789 ] Formatted preview: 123,456,789
And as the input box is keyup'd, the formatted preview is refreshed.
I personally think this strikes the right balance, but I was curious what other good solutions the folks here on HN have seen to this problem.
Thanks for your comment ^_^
- fuzzfactor 4y agoI would de-emphasize the formatted preview, locate it further from the input field and use smaller font for instance. Computer input was never intended to have commas. Recent Microsoft Calculator versions that display (and copy/paste!) the commas are a ridiculous failure compared to the original approach. The best fonts are those where there can no confusion between 1, I, & l or O, o, & 0. If you make it big enough for someone with poor vision to be able to see without their glasses, there will be fewer mistakes too. Also for consistency make all big numbers throughout your site text comma-free to serve as something of an example.
- herodoturtle 4y agoThanks for this :-)