summaryrefslogtreecommitdiffstats
path: root/wiki/src/blueprint/cleanup_iceweasel_prefs.mdwn
blob: 8b57da75208c22f0e99e1cc25f57fce974cc4cd3 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
[[!toc levels=2]]

Relevant ticket: [[!tails_ticket 5768]]

# not displayed in about:config

We set these settings in our config files, but they don't appear in about:config:

* browser.bookmarks.livemark_refresh_seconds
* browser.history_expire_days
* browser.history_expire_days.mirror
* browser.microsummary.updateGenerators
* browser.safebrowsing.remoteLookups
* browser.sessionstore.enabled
* capability.policy.maonoscript.javascript.enabled
* capability.policy.maonoscript.sites
* extensions.update.notifyUser
* pref.privacy.disable_button.cookie_exceptions
* pref.privacy.disable_button.view_cookies
* pref.privacy.disable_button.view_passwords
* privacy.item.offlineApps
* privacy.item.passwords
* privacy.sanitize.didShutdownSanitize
* privacy.sanitize.promptOnSanitize
* security.disable_button.openCertManager
* security.enable_java
* security.enable_ssl2
* signon.prefillForms
* xpinstall.whitelist.add.103

Most of these settings are probably obsolete.

We should verify this and remove them from our configuration.

# different value in about:config than in our configuration files

* `browser.chrome.site_icons`: not set by the TBB / Torbutton; let's research if we really want to set it to a non-default value.
* `extensions.update.autoUpdateDefault`: not set by the TBB / Torbutton; let's research if we really want to set it to a non-default value.
* `noscript.subscription.lastCheck`: research if the value is expected to be modified at runtime
* `extensions.torbutton.startup`: expected to be set to false, as `torbutton_do_startup()` sets this to false after it has done its job.
* `browser.startup.homepage_override.buildID` is set to the build time of Iceweasel on startup. The same happens in TBB, so we can probably just ignore this.
* `browser.startup.homepage_override.mstone` same as above, but set to the version (e.g. 17.0.5). The same happens in TBB, so we can probably just ignore this.