Closed
Bug 1449009
Opened 7 years ago
Closed 7 years ago
Non-localized strings on Customize -> Themes dropdown, if any theme but 'Default' is selected
Categories
(Firefox :: Toolbars and Customization, defect)
Firefox
Toolbars and Customization
Tracking
()
RESOLVED
DUPLICATE
of bug 658044
People
(Reporter: itiel_yn8, Unassigned)
Details
STR:
1. Use any non-english build of Nightly
2. Open the customization page
3. Click 'Themes'
4. Select 'Dark' for exaple
5. Click 'Themes' again
AR:
The 'Default' text and its tooltip are now back to English.
ER:
Both should remain in the localized versions. Reverting back to Default fixes this.
Comment 1•7 years ago
|
||
Is this a regression, or has it always been broken?
Off-hand, I don't understand how/why this would happen - we always get the theme name off the theme object, here:
https://dxr.mozilla.org/mozilla-central/rev/de32269720d056972b85f4eec5f0a8286de6e3af/browser/components/customizableui/CustomizeMode.jsm#1367
so I don't see why this would change based on which theme is selected... does the same thing happen in the add-ons manager?
Flags: needinfo?(itiel_yn8)
(In reply to :Gijs from comment #1)
> Is this a regression, or has it always been broken?
I know this has been there for a long time, though not sure if that's a regression or not. Investigating.
(In reply to :Gijs from comment #1)
> does the same thing happen in the add-ons manager?
Yes. The string(s) get non-localized when I change the theme to non-default, and after reverting back to Default and reloading the add-ons manager page, it gets back to my locale.
Comment 3•7 years ago
|
||
I believe this is a dupe of bug 1402719, not sure if it's even older than that.
Comment 4•7 years ago
|
||
(In reply to Francesco Lodolo [:flod] (workweek until Mar 30, slower than usual) from comment #3)
> I believe this is a dupe of bug 1402719, not sure if it's even older than
> that.
Yeah, there's a comment in there. Thanks!
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(itiel_yn8)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•