firefox-bin-20.0 and later (at least on x86) forces the "use system colors" preference via the /opt/firefox/all-gentoo.js file. At every restart of the application this file overrides the user preference set via the preferences dialog from the application GUI. This behaviour seems rather unnecessary.
OK, something weird. I reverted to firefox-bin-17.0.5-r1, and now it is doing it too! I never saw this problem before installing firefox-bin-20.0, so now I am confused.
Spoke too soon ... firefox-bin-17.0.5-r1 seemed to be broken too, but after a couple of restarts it behaved as expected, preserving my preference to not use system colors.
Arrrghh!!! OK, so 17.0.5-r1 really is doing it too. I am so confused about what is happening, and am going to just shut up now and wait for someone smart to come along.
Created attachment 346060 [details] packages.gentoo.org with system_colors on Screenshot that shows how this setting affects rendering with dark color schemes (kde -> Obsidian Cost): many parts are hard (if at all) to read. But I think this is an error in firefox. User settings should be considered last.
Created attachment 346062 [details] packages.gentoo.org with system_colors disabled
I can confirm this problem. The setting is in /opt/firefox/all-gentoo.js and interferes with dark themes. pref("browser.display.use_system_colors", true); This overrides every other setting for this preference. For a while I was manually changing it in preferences until I discovered the file. On emerged updates to the package, I found I have to edit it again. I learned about it via Mozilla support: http://support.mozilla.org/en-US/questions/956231 It's actually a problem with Thunderbird as well.
pref sets a default for the preference, you can always change it, it's not lockPref.
Sure, you can change it, but the change does not persist. Changing it every time you start the browser gets old fast. Can someone explain why forcing this preference on everyone is considered desirable?
I agree, that's not an acceptable answer. Until I changed the gentoo.js file, I had to change it every time I restarted the browser, and that was obnoxious. I tried to override it in prefs.js in the profile but it is overridden by gentoo.js. At the very least, gentoo.js should call a local config file that overrides this (if possible) and document it somewhere so people aren't left scratching their heads, with very little to go on besides one solution buried in Mozilla's support forums.
> Can someone explain why forcing this preference on everyone is considered > desirable? The intent is to set the default, not to force the preference setting at every run. If that's not what is happening then there is a bug here.
This continues to annoy me with Mozilla's frequent release cycles. I've had to resolve this by putting CONFIG_PROTECT="/opt/firefox/all-gentoo.js in my make.conf file.
(In reply to A.J. from comment #11) > This continues to annoy me with Mozilla's frequent release cycles. I've had > to resolve this by putting CONFIG_PROTECT="/opt/firefox/all-gentoo.js in my > make.conf file. why don't you just set the option in your user's prefs.js then? about:config search set to false profit!
(In reply to Ian Stakenvicius from comment #12) > why don't you just set the option in your user's prefs.js then? > > about:config > search > set to false > profit! I don't think you tried this. prefs.js was one of the first things I tried to use to override it, and part of why I was annoyed at being forced to someone else's standards. Just tested your steps several times. No profit. No soup for you. No deal. I believe this has to do with whereever all-gentoo.js is sourced that overrides any personal changes, and therefore is fully a bug.
browser.display.use_system_colors that you set via about:config is just the same thing that the GUI button toggles. It is, as stated in the OP and since, overwritten by the all-gentoo.js file at every restart. The only cure is to remove it from all-gentoo.js .
hmm... yes. i am thinking this must have to do with the way "general.config.file" gets handled. i will try some experiments with moving settings from all-gentoo.js into defaults/pref/local-settings.js and see if that helps matters.
24.1.1 is now stable ... still has same problem.
24.3.0, still doing it.
Several sources [1,2] refer that pref() explicitly overrides the user-set setting every time Firefox is started. defaultPref() is described as what sets a *default*. This is probably what is wanted at leat for this setting.
Several sources [1,2] refer that pref() explicitly overrides the user-set setting every time Firefox is started. defaultPref() is described as what sets a *default*. This is probably what is wanted at least for this setting. [1] https://support.mozilla.org/en-US/questions/956231 [2] http://mike.kaply.com/2012/03/16/customizing-firefox-autoconfig-files/
Created attachment 373570 [details, diff] Change all-gentoo.js to use defaultPref() instead of pref() for "use system colors" This changes all-gentoo.js to set only the default value for browser.display.use_system_colors, instead of forcing the setting to "true" on startup. It may be desired to evaluate if the same is needed for other settings. Works at least with =www-client/firefox-bin-24.4.0. This still needs the setting to be changed *after* firefox-bin has been updated, but this time the setting will persist across firefox shutdowns.
28.0-r1 is in the tree. I have changed a few prefs to defaultPref along with adding additionally setting default dictionary path that can be changed by user as well.
Created attachment 373810 [details, diff] Patch for new all-gentoo.js (In reply to Jory A. Pratt from comment #21) > 28.0-r1 is in the tree. I have changed a few prefs to defaultPref along with > adding additionally setting default dictionary path that can be changed by > user as well. The new all-gentoo.js seems to have an unexpected ending, causing Firefox fails to start.
Comment on attachment 373810 [details, diff] Patch for new all-gentoo.js >--- a/portage/www-client/firefox-bin/files/all-gentoo-1.js >+++ b/portage/www-client/firefox-bin/files/all-gentoo-1.js >@@ -4,7 +4,7 @@ > lockPref("intl.locale.matchOS", true); > // Allow user to change based on needs > defaultPref("browser.display.use_system_colors", true); >-defaultPref("spellchecker.dictionary_path", "/usr/share/myspell" >+defaultPref("spellchecker.dictionary_path", "/usr/share/myspell"); > defaultPref("browser.shell.checkDefaultBrowser", false); > // Preferences that should be reset every session > pref("browser.EULA.override", true);
28.0-r1 is broken for me. Browser will not start after update, deleted ~/.mozilla and it crashes just after the screen that asks you to import settings.
(In reply to vekin from comment #24) > 28.0-r1 is broken for me. Browser will not start after update, deleted > ~/.mozilla and it crashes just after the screen that asks you to import > settings. This has already been fixed early this morning, resync and re-emerge firefox-bin and you will be fixed.
