Re: [whatwg] Should navigator.language and and/or HTTP Accept-Language include locale?
I propose to standardize locale settings (datetime, number delimeters) can be specified only by user via the operating system settings. Sites should not change the locale that the user has chosen for himself. -- Best Regards, Mike Gavrilov. 2016-05-25 10:15 GMT+05:00 Anne van Kesteren : > On Wed, May 25, 2016 at 4:50 AM, Geoffrey Garen wrote: >> My claim is that if you want English language with Russian regional settings >> then browsers must report “en-ru” in navigator.language. > > That doesn't work. What if you want British English and the Russian > locale? Or Canadian French with the US locale? A language tag already > uses that syntax to mean something else. You can't just repurpose it > to indicate locale. > > > -- > https://annevankesteren.nl/
Re: [whatwg] Should navigator.language and and/or HTTP Accept-Language include locale?
I'm afraid that bind regional setting to interface language is not correct. For example, I prefer the English language interface (it's easier to write bug reports, search in Google documentation), but I need the russian regional settings (number format, date format and time format) for input controls. Expected behaiour that regional settings would be inherited from OS settings. -- Best Regards, Mike Gavrilov. 2016-05-24 11:08 GMT+05:00 Anne van Kesteren : > On Tue, May 24, 2016 at 1:55 AM, Nils Dagsson Moskopp > wrote: >> • navigator.language is the language of the interface >> • HTTP Accept-Language is the language of content >> • ECMA-402 DefaultLocale() is the user's locale > > The HTML Standard has a should-level requirement for the first two to > align, to avoid fingerprinting vectors. Also, Accept-Language is the > desired language, it's a request header, which navigator.language is > just the API for (and navigator.languages is the more complete API > for). Perhaps you're thinking of Content-Language. > > > -- > https://annevankesteren.nl/
Re: [whatwg] Proposal for showing thousand separator in form controls.
Frankly I do not understand it means, yes or no? I am first time here. How did approval procedure takes place? Anything else I need to do or describe final idea? Any examples how make this better. Thanks. -- Best Regards, Mike Gavrilov. 2015-10-15 20:30 GMT+05:00 Boris Zbarsky : > On 10/15/15 9:58 AM, Михаил Гаврилов wrote: >> >> I understand an option to add an attribute to manually specify a >> delimiter is not considered here. > > > I think this is the thing that has the best chance of success: having > explicit opt-in to various different formatting behaviors based on knowledge > of what sort of "number" you're showing. > > -Boris
Re: [whatwg] Proposal for showing thousand separator in form controls.
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 - use local settings for delimeter 1,234 - use for removing thousand delimiter 1234 - 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 : > 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 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 is unfortunate. > > -Boris
Re: [whatwg] Proposal for showing thousand separator in form controls.
I'm afraid that we have never agreed until someone misused . Let's first decide what numbers is meant by number type. If our answer would be: https://en.wikipedia.org/wiki/Rational_number The years is the smallest part of all the numbers. Anyway always can use for them. 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. -- Best Regards, Mike Gavrilov. 2015-10-14 18:11 GMT+05:00 Boris Zbarsky : > On 10/14/15 5:47 AM, Михаил Гаврилов wrote: >> >> 2015-10-14 0:41 GMT+05:00 Boris Zbarsky : >>> >>> See https://bugzilla.mozilla.org/show_bug.cgi?id=974175 for details. >> >> >> I think the problem with the display of the year with the help of >> far-fetched. > > > In what sense? People are doing it right now, and people do not expect to > see "2,015" as the year. They just don't. > >> Sooner or later year will be five-digit and more > > > You mean "later", right? ;) Seriously, I expect the computer interaction > modalities to be quite different by then, assuming the concept even makes > sense at that point. > >> And in general I think for selecting date should be used for >> special types of input: type="month" type="year". > > > That's great, and I agree, but that's not what people are doing in practice. > > -Boris
Re: [whatwg] Proposal for showing thousand separator in form controls.
2015-10-14 0:41 GMT+05:00 Boris Zbarsky : > See https://bugzilla.mozilla.org/show_bug.cgi?id=974175 for details. I think the problem with the display of the year with the help of far-fetched. Sooner or later year will be five-digit and more, and 85321 year will be better to look like 85,321. And in general I think for selecting date should be used for special types of input: type="month" type="year". -- Best Regards, Mike Gavrilov.
[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.
