874908 - L20n don't switch language correctly.

Status: RESOLVED WORKSFORME

(L20n :: JS Library, defect, P2)

Description

[Silent Imp]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.93 Safari/537.36

Steps to reproduce:

I try to switch between russian and english language.
Manifesto:
{
  "languages": [
    "en-GB",
    "ru-RU"
  ],
  "resources": [
    "language/{{lang}}/data.l20n"
  ]
}


Actual results:

When Accept-Language header is set to "ru" — "ru-RU" just don't work


Expected results:

When Accept-Language header is set to "ru" it should switch to russian language.

Comment 1

[Staś Małolepszy :stas]

It looks like Intl.prioritizeLocales doesn't match "ru" in the Accept-Language header with "ru-RU" in the manifest.

Gandalf, is this expected?

Comment 2

[Silent Imp]

Header in Chrome:
Accept-Language:ru,en;q=0.8,en-US;q=0.6

Headers in Firefox:
Accept-Language:ru,en-us;q=0.7,en;q=0.3

Comment 3

[Zibi Braniecki [:zbraniecki][:gandalf]]

The reason why this doesn't work is because your app reports to support only en-GB flavor which is more specific than what your user requests.

The Ecma 402 ( http://ecma-international.org/ecma-402/1.0/ ) does not support such scenario.

What you should do is provide "ru" language and then both "ru-RU" and "ru" in request will match it.

Comment 4

[Zibi Braniecki [:zbraniecki][:gandalf]]

Saying that, I see a limitation of language tag not being canonicalizied and that we return wrong lists of matching locales.

I filed bug 879997 to update that.

Comment 5

[Zibi Braniecki [:zbraniecki][:gandalf]]

Reporter, can you confirm that the behavior with the latest commit matches your expectations?

Comment 6

[Zibi Braniecki [:zbraniecki][:gandalf]]

closing for now. If the bug still exists, please, reopen.

Comment 7

[Zibi Braniecki [:zbraniecki][:gandalf]]

clearning NI