327446 - Cannot switch extensions' UI locale

Status: RESOLVED INCOMPLETE

(Thunderbird :: General, defect)

Description

[Rod Whiteley]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Thunderbird version 1.5 (20051201)

Thunderbird does not switch extensions' UI locale when you start it using -UILocale in the command line, or when you use Config Editor to set the general.useragent.locale preference.

Reproducible: Always

Steps to Reproduce:
1. In Thunderbird (en-US), install an extension that supports fr-FR
2. Start Thunderbird using -UILocale fr-FR

Actual Results:  
The extensions's UI remains in English.

Expected Results:  
The extension's UI should now be in French.

Firefox 1.5 does not have this problem.

Workarounds are: delete XUL.mfl before starting Thunderbird with a new locale, or set the nglayout.debug.disable_xul_cache pref to true.

Opening a dialog sometimes cures the problem.  The dialog unxpectedly appears in the correct language, then after the next restart everything is in the correct language.

An example extension that supports fr-FR is Mozilla alendar 0.2,  the "Stable Build" at:  http://www.mozilla.org/projects/calendar/download.html#download_thunderbird

Comment 1

[Rod Whiteley]

Attachment: Test extension (en-US and fr-FR)

Test extension supports en-US and fr-FR in Firefox and Thunderbird

Comment 2

[Mike Cowperthwaite]

This appears to be the same as Firefox bug 327650.

Robert, note there is a test case here.

Comment 3

[Robert Strong (they/them - no direct email)]

(In reply to comment #2)
> This appears to be the same as Firefox bug 327650.
This is actually a different bug

Comment 4

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Reporter, does the issue still occur in the latest supported 2.0.0.x / Shredder trunk nightlies?

(1.5.0.x is now end-of-life and the latest supported 2.0.0.x is version 2.0.0.16)

Comment 5

[Joshua Cranmer [:jcranmer]]

RESO INCO per lack of response to question in last comment. If you feel this change was made in error, please respond to this bug with your reasons why.