Privacy.sanitize.sanitizeOnShutdown mozilla bug ?
See original GitHub issuein privafox “privacy.sanitize.sanitizeOnShutdown” is defaulted to true…
when the config file is used normally with pref("privacy.sanitize.sanitizeOnShutdown", true);
the setting is not applied
when used with mozilla.cfg the setting is enforced BUT its value is string type even if it’s set true without quotes… (but the setting work even if its a wrong var)
to be able to default this settings the used value is string so pref("privacy.sanitize.sanitizeOnShutdown", "true");
it works but the side effect is this option can not be disabled in the ffox settings anymore and the gui show a wrong value.
in short this seems to be a ffox bug where this value is incorrectly set to string instead of bool.
This could affect ghacks too where the setting is just ignored… when set without quotes which is the case.
Any way temporary solution is set with quotes
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top GitHub Comments
Yes i did checked also in ghack script and found it working it’s why i did not report it back… Indeed i encountered about 4 or 5 similar cases while enforcing/defaulting settings in the cfg file… it’s one of the reason v2 is delayed… but i figure it our finally 😃
Nope. It works as advertised from a user.js. I just tested in a nilla FF65. I did change to custom settings in Options>Privacy & Security>History>Firefox will use
<custom settings>
so I could see the “clear history when firefox closes” was unchecked.Added the following user.js
Closed and reopened FF, and the value true was applied in about:config (and in prefs.js), and the parrot worked as expected. In options, the setting “Clear history when Firefox closes” was now checked.
The issue must lie with cfg. It’s not the first pref I’ve heard of that has issues there, but not in user.js