-
Notifications
You must be signed in to change notification settings - Fork 81
Manually editing per site switches
You can manually edit rules for per-site switches in the "My rules" pane in the dashboard.
There are no temporary vs. permanent settings for the per-site switches, any change to one or more switches will be immediately reflected in the permanent settings.
There are currently three per-site switches supported:
-
no-popups
: To block all popups. -
no-strict-blocking
: To disable strict blocking. -
no-cosmetic-filtering
: To disable cosmetic filtering.
When toggled through the popup UI, these switches will apply only to the current web site. However you can edit them manually using the "My rules" pane in the dashboard.
The syntax is as follow:
switch-name: hostname state
The switch name must be followed by a column :
, a space, then the hostname on which the switch must apply. Use *
as a hostname placeholder to indicate you want the switch to apply everywhere. Following is the state of the switch, which can be on
or off
(true
or false
are also valid).
When switches share a common hostname ancestor, the most specific wins. For example, if you have:
no-popups: example.com on
no-popups: www.example.com off
and you visit www.example.com
, the "no popups" switch will be turned off (popup allowed unless blocked by a static filter).
All switches are off
by default, meaning there is no point in creating an entry such as:
no-popups: www.example.com off
Unless it is to override a related broader entry for which the switch is on
.
- Chromium-based browsers: If you block popups everywhere by default (
no-popups: * true
), this will break "Open link in new tab" in the context menu. This is because of Chrome API limitations.
- 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