The file /opt/firefox/defaults/pref/firefox.js that comes with mozilla-firefox-bin is not consistent with /usr/lib/mozilla-firefox/defaults/pref/firefox.js that comes with mozilla-firefox. In particular, signon.prefillForms is set to a default of true for mozilla-firefox-bin and false for mozilla-firefox. This is an issue for AMD64 users who often have both installed. A user might set the signon.prefillForms to true in his about:config in mozilla-firefox, and then open up mozilla-firefox-bin. mozilla-firefox-bin seeing this value set to what it sees as a default, doesn't bother to resave it in the user's prefs.js on close, meaning that when that user reopens mozilla-firefox, it doesn't see the value in prefs.js and assumes IT'S default of false. Doing a diff between the two files signon.prefillForms seems to be the only value that is inconsistent like this. A workaround is to simply change /opt/firefox/defaults/pref/firefox.js's signon.prefillForm value to false. Reproducible: Always Steps to Reproduce: 1. In mozilla-firefox in about:config set signon.prefillForms to true. Close mozilla-firefox 2. Open and close mozilla-firefox-bin. 3. Reopen mozilla-firefox and check the signon.prefillForms in about:config. Actual Results: The value flipped to false. Expected Results: The value should've stayed true.
/opt/firefox/defaults/pref/firefox.js contains whatever is the upstream default.
The shouldn't mozilla-firefox be the one changed then?
No, it shouldn't. Noone ever told you that upstream defaults will be consistent with Gentoo ones, so pick up one ebuild or the other.
There are reasons to have both installed. 32-bit firefox can't talk to a 64-bit GNOME and GNOME application preferences and is therefore unsuitable for constant usage. But you can't run Flash on 64-bit Firefox. These too have preferences that differ for basically no reason and it causes a bug.
Sigh. We won't be mangling upstream defaults in -bin; live with it and don't use bin if you dislike it.
