Closed
Bug 1203784
Opened 9 years ago
Closed 9 years ago
Having extensions installed revert selected theme to default one
Categories
(Firefox :: Theme, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: antonio_mario_novo, Unassigned)
Details
User Agent: Mozilla/5.0 (masking-agent; rv:42.0) Gecko/20100101 Firefox/42.0
Build ID: 20150910030225
Steps to reproduce:
Using a clean/new profile:
1) Install a lightweight theme (any, example: https://addons.mozilla.org/en-us/firefox/addon/transparent-firefox/), and set the newly installed theme to be used;
2) Install an extension/add-on (any, dictionaries included, example: https://addons.mozilla.org/en-us/firefox/addon/united-states-english-spellche/)
3) Restart Firefox
Actual results:
After restarting Firefox, the selected lightweight theme as reverted back to the default one. Re-selecting any other lightweight theme and restarting has the same results.
Expected results:
Firefox should have maintained the theme selected by the user, without reverting back to the default one after each restart.
Note: this only happens with lightweight themes, the developer theme is not affected (stays in use after restart if selected).
Seems like a regression only on the last nightly release, right now it's either have no extensions, only use the default theme or have to re-select the desired theme after each browser restart.
Comment 1•9 years ago
|
||
Reproduced in nightly on Ubuntu 14.04. Theme resets itself to default on restart.
Gerv
Status: UNCONFIRMED → NEW
Component: Untriaged → Theme
Ever confirmed: true
Reporter | ||
Comment 2•9 years ago
|
||
The latest Nightly build (https://hg.mozilla.org/mozilla-central/rev/039a8490891595736b16a3ccb17f025f4dcf13eb) seems to have fixed this, selected theme stays in use after browser restarts.
Can someone else confirm this, and if so close the bug?
Reporter | ||
Comment 3•9 years ago
|
||
Since no one reported anything, it seems like this is not an issue anymore.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•