[whatwg] Proposal: Locale Preferences API

Ian Hickson ian at hixie.ch
Fri Jan 31 13:58:01 PST 2014


On Thu, 12 Dec 2013, Jungshik Shin (신정식, 申政湜) wrote:
> 2013/11/27 Boris Zbarsky <bzbarsky at mit.edu>
> > On 11/27/13 4:28 PM, Jungshik Shin (신정식, 申政湜) wrote:
> >
> >> That is, I suggest that 'navigator.language' always be the UI 
> >> language of a web browser.
> >
> > That's an unacceptable privacy leak from Mozilla's point of view.  
> > See https://bugzilla.mozilla.org/show_bug.cgi?id=55366 where we 
> > explicitly switched from that to basing navigator.language on the 
> > Accept header.
>
> Well, the vast majority of users would never touch A-L list. So, the top 
> entry in the A-L list would remain the default value, which is usually 
> the UI language. So, I don't know how much your change helps privacy if 
> revealing the UI language is indeed a valid privacy concern.

On Fri, 13 Dec 2013, Boris Zbarsky wrote:
> 
> The point is, the Accept-Languages header already reveals whatever it 
> reveals, so there is no additional privacy leak from navigator.language 
> if you just mirror what the header.  And for people who _do_ change the 
> A-L list, they get it picked up in both places automatically.

It does seem reasonable that the three APIs (the header and the two IDL 
attributes, one giving one value and the other a list) would expose the 
same information, or at least subsets thereof (for the single value one).

Jungshik, is there any particular reason for _not_ doing this?

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'


More information about the whatwg mailing list