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.
> --

Received on Tuesday, 24 May 2016 06:21:20 UTC