Closed
Bug 1026746
Opened 12 years ago
Closed 12 years ago
L20n.js on Chromium - always use the default language
Categories
(L20n :: JS Library, defect)
L20n
JS Library
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 886053
People
(Reporter: noemie.lehuby, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release)
Build ID: 20140608211208
Steps to reproduce:
I try to localize my website under several languages : fr (default), es and ast.
Actual results:
With Chromium, the website uses the fr chains only, no matter the browser config.
With Firefox, it's ok, if the browser language is set to es, the es chains are used.
Chromium Version 34.0.1847.116 Ubuntu 13.10 (260972)
Accept-Language:es,en-US;q=0.8,en;q=0.6
Expected results:
The es chains should be used when viewing my website with Chromium too.
Comment 1•12 years ago
|
||
Hi there, thanks for the report. Unfortunately, if I understand the issue correctly, this is a bug in Chrome/Chromium, not L20n. In Chromium, navigator.language is always set to the language of the UI of the browser (which depends on the build that you install) instead of being the first value of the Accept-Languages pref.
In the future, we'll want to use navigator.languages anyways, but I'm also not sure what the status of the implementation in Chromium is.
See https://code.google.com/p/chromium/issues/detail?id=101138 and bug 886053.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Comment 2•12 years ago
|
||
(In reply to Staś Małolepszy :stas from comment #1)
> In Chromium,
> navigator.language is always set to the language of the UI of the browser
> (which depends on the build that you install) instead of being the first
> value of the Accept-Languages pref.
Note that this was the case for a really long time in Firefox as well, as that was the original intent of navigator.language - we switched away from that mostly because of how websites were using it, IIRC.
You need to log in
before you can comment on or make changes to this bug.
Description
•