-
Notifications
You must be signed in to change notification settings - Fork 81
Privileged Pages
Privileged Pages are the webpages that browser-vendors consider as an entitled webpage/s where extensions are tasked to not work/have their functionality ceased entirely.
For Chromium1:
clients.google.com
clients[0-9]+.google.com
sb-ssl.google.com
chrome.google.com/webstore/*
- On the aforementioned domain, all Chromium/Chrome extensions will cease their functionality.
For Firefox2:
accounts-static.cdn.mozilla.net
accounts.firefox.com
addons.cdn.mozilla.net
addons.mozilla.org
api.accounts.firefox.com
content.cdn.mozilla.net
discovery.addons.mozilla.org
install.mozilla.org
oauth.accounts.firefox.com
profile.accounts.firefox.com
support.mozilla.org
sync.services.mozilla.com
-
Just like Chrome, Firefox's WebExtensions will also cease to work on these aforementioned domains.
-
To allow WebExtensions in Firefox to run on these pages(at your own risk), open
about:config
and modify the following 3 :- Set
extensions.webextensions.restrictedDomains
to be an empty string.4 - Set
privacy.resistFingerprinting.block_mozAddonManager
totrue
.5- Firefox 60 - Firefox 70: must be manually created by right clicking and selecting New > Boolean3
- Firefox 71 and newest6: paste preference name in search bar > in 2nd column set Boolean from single-choice list > click ➕ button in 3rd column.
- Set
[1] stackoverflow.com, chrome_extensions_client.cc, extension_urls.cc, web_request_permissions.cc
[2] https://hg.mozilla.org/mozilla-central/rev/39e131181d44
[3] https://www.ghacks.net/2017/10/27/how-to-enable-firefox-webextensions-on-mozilla-websites/
[4] https://bugzilla.mozilla.org/show_bug.cgi?id=1445663#ch-3
[5] https://bugzilla.mozilla.org/show_bug.cgi?id=1310082#c24
[6] https://www.ghacks.net/2019/11/11/firefox-71-new-aboutconfig-interface-lands/
- Wiki home
- About the Wiki documentation
- Permissions
- Privacy policy
- Info:
- The toolbar icon
- The popup user interface
- The context menu
-
Dashboard
- Settings pane
- Filter lists pane
- My filters pane
- My rules pane
- Trusted sites pane
- Keyboard shortcuts
- The logger
- Element picker
- Element zapper
-
Blocking mode
- Very easy mode
- Easy mode (default)
- Medium mode (optimal for advanced users)
- Hard mode
- Nightmare mode
- Strict blocking
- Few words about re-design of uBO's user interface
- Reference answers to various topics seen in the wild
- Overview of uBlock's network filtering engine
- uBlock's blocking and protection effectiveness:
- uBlock's resource usage and efficiency:
- Memory footprint: what happens inside uBlock after installation
- uBlock vs. ABP: efficiency compared
- Counterpoint: Who cares about efficiency, I have 8 GB RAM and|or a quad core CPU
- Debunking "uBlock Origin is less efficient than Adguard" claims
- Myth: uBlock consumes over 80MB
- Myth: uBlock is just slightly less resource intensive than Adblock Plus
- Myth: uBlock consumes several or several dozen GB of RAM
- Various videos showing side by side comparison of the load speed of complex sites
- Own memory usage: benchmarks over time
- Contributed memory usage: benchmarks over time
- Can uBO crash a browser?
- Tools, tests
- Deploying uBlock Origin
- Proposal for integration/unit testing
- uBlock Origin Core (Node.js):
- Troubleshooting:
- Good external guides:
- Scientific papers