angela 70c11d8503 Disable webp on Firefox added | 3 years ago | |
---|---|---|
.. | ||
.mozilla | 3 years ago | |
img | 4 years ago | |
README.md | 4 years ago | |
disable-webp-firefox.md | 3 years ago | |
firefox-disable-doh.md | 4 years ago | |
firefox-disable-fat-url-bar.md | 3 years ago | |
remove-print-headers.md | 4 years ago | |
restoring-statusbar.md | 3 years ago | |
setup-browsing-profiles.md | 4 years ago |
The about:config
setting for privacy.firstparty.isolate collides with Cookie Auto-Delete and prevents it from working. Setting it to false regains Cookie Auto-Delete's capabilities.
On Firefox 60 ESR, I first ran into this garbage:
This is a privileged page, whose permissions cannot be configured.
To get rid this nuisance, modify about:config settings:
about:config
Create the following boolean if it doesn't exist:
bash
privacy.resistFingerprinting.block_mozAddonManager
Enter boolean value:
Also empty the following (choose yourself what to whitelist):
extensions.webextensions.restrictedDomains
This appears to be a "hidden" setting meant for Tor, according to the extensions API:
static bool IsValidHost(const nsACString& host) {
// This hidden pref allows users to disable mozAddonManager entirely if they
// want for fingerprinting resistance. Someone like Tor browser will use this
// pref.
if (Preferences::GetBool(
"privacy.resistFingerprinting.block_mozAddonManager")) {
return false;
}
https://dxr.mozilla.org/mozilla-central/source/toolkit/mozapps/extensions/AddonManagerWebAPI.cpp