1216517 - The developer edition theme does not enable in the first enable action when third-party theme is enabled

Status: RESOLVED INACTIVE

(Toolkit :: Add-ons Manager, defect)

Description

[magicp]

Attachment: The developer edition theme does not enable in the first time.mp4

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:44.0) Gecko/20100101 Firefox/44.0
Build ID: 20151019030227

Steps to reproduce:

1. Start Aurora (or Nightly) which is enabled a third-party theme
2. Open Add-ons Manager (about:addons) > Appearance
3. Click "Enable" button of the Developer Edition theme


Actual results:

The developer edition theme does not enabled in the first enable action. (The default theme is enabled). And also "Enable" button is still enable. 


Expected results:

The developer edition theme should be enabled in the first enable action.

Comment 1

[Tony Mechelynck [:tonymec]]

Firefox's "Default" and "Developer Edition" themes have some special relation to each other which makes the switch between them restartless. AFAIK any other switch between complete themes (including SeaMonkey's "Default" and "Modern") requires a restart.

However, after step 3, the entry for Developer Edition in the add-ons manager ought to say "√ Developer Edition will be enabled after you restart Firefox    Restart now    Undo". IIUC what is said in comment #0, it doesn't.

What I see is slightly different (or maybe I misunderstood?). At step 3, before restarting, everything looks normal in the addons manager. But after I click "Restart Now" on the Development Edition entry (and wait for the restart to happen), the default theme's look and feel is displayed, but all themes (in my case, Default, Developer Edition and LCARStrek) show up as "disabled". An additional click on "Enable" for Developer Edition (without restart) is needed to display it.

This is the build O tested:
UA:"Mozilla/5.0 (X11; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0" (en-US) ID:20151225030207 CSet:35b211eaad1fa828064514c547057e4400e24459

Comment 2

[BMO Automation]

Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.