Add-on/extension (e.g. default theme) name and description not localized by pref if its disabled, affects customization e.g. in Firefox Developer Edition

UNCONFIRMED
Unassigned

Status

()

Toolkit
Add-ons Manager
P5
normal
UNCONFIRMED
a year ago
8 months ago

People

(Reporter: aryx, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: triaged)

E.g. latest 53.0a2 on Windows 8.1

Add-ons which have a localized name and description and this setting
>pref("extensions.<id>.name/description", "chrome://<path>/<file>.properties");
and
>extensions.{972ce4c6-7e08-4474-a285-3208198ce6fd}.name/description=My Extension Name
in the file don't have it localized if it's disabled (at least after a restart).

This also affects the default theme.

Steps to reproduce:
1. Use a localized build (developer edition is the easiest).
2. If you don't have the developer edition, open the Add-ons Manager and install a theme from the top-most pane.
Actual result:
- In the theme list, the default theme will now have an English name and description (works the first time, sometimes later it might a require a restart).
- In the customization mode from the hamburger menu on the right side of the toolbar, these English strings are used as label and tooltip in the theme menu at the bottom.

Comment 1

a year ago
in 57 this will work with webextensions.
Status: NEW → UNCONFIRMED
Ever confirmed: false
Flags: needinfo?(amckay)
Priority: -- → P5
Sorry, to be clearer, will this be relevant in Desktop release once we only support WebExtensions? I don't think so.
Flags: needinfo?(amckay)

Comment 3

a year ago
(In reply to Andy McKay [:andym] from comment #2)
> Sorry, to be clearer, will this be relevant in Desktop release once we only
> support WebExtensions? I don't think so.

I think it will, because the default theme will still be affected per comment #0, and at least for the moment I expect that'll keep being reflected as a 'complete' theme in the add-ons manager. I would be surprised if we were able to strip all the relevant code out immediately for 57, but maybe I'm wrong. Dave would have a better idea about this.
Flags: needinfo?(dtownsend)
Once complete themes are gone this shouldn't be an issue but we should verify that.
Flags: needinfo?(dtownsend)

Comment 5

11 months ago
checking what our default theme is going to be with Photon- to understand what different kindso are.
Flags: needinfo?(rhelmer)
Whiteboard: investigating

Comment 6

10 months ago
rob will ask mossop what he meant - think won't be issue beyond 57

Comment 7

9 months ago
rob have you talked to mossop
Flags: needinfo?(rhelmer)
Sorry for the delay. I believe this will still be an issue post-57 (what Gijs says in comment 3) because Dave is right in comment 4 that removing complete theme support will fix this but I don't know that we're going to have that removed in time for 57 (seems like the minimum bar would be to refuse to load themes for 57, and not accept them on AMO anymore etc)

I'm assuming this is a long-standing bug and while annoying is pretty low in severity, so while we probably won't get the above done in time for 57 I think it will go away soon since we definitely want to remove all the complete theme code from the addons manager.

Updated

9 months ago
Whiteboard: investigating → triaged

Updated

8 months ago
Duplicate of this bug: 1379435
You need to log in before you can comment on or make changes to this bug.