Quick guide: popup user interface
- The title bar
- The large power button
- The number of requests blocked
- The number of domains connected
- The site-based switches
This is uBlock's popup UI when you click on uBlock's icon in the toolbar:
Click the title bar of the popup to go to uBlock's dashboard.
Click the large power button to turn off uBlock for the current site (a.k.a. whitelist the current site). This will be remembered the next time you visit the site.
Alternatively, you can also Ctrl-click to turn off uBlock only for the current page (command ⌘-click on Mac).
For more advanced whitelisting control, see "How to whitelist a web site".
This shows the number of network requests which were blocked on the current page. Also, less useful, but people like this kind of thing, the number of network requests blocked since install.
Click the eye-dropper icon to enter element picker mode, which allows to create a filter by interactively picking an element on a page, in order to have the element permanently removed from the page.
Click the eye icon to bring up the network request logger, which will open in a separate tab. This allows to inspect real-time network traffic on a given page.
The number of distinct domains with which a network connection was established, out of all connections (established + blocked). The domains are derived using the official Public Suffix List.
In general, it must be assumed that each distinct domain is managed by a distinct administrative authority. In practice, it is not uncommon to have a couple distinct domains which are under the same administrative authority (for example: google.com, ajax.googleapis.com and gstatic.com, or wikipedia.org and wikimedia.org).
That said, this statistic has to be seen this way: the more distinct domains your browser connects to, the larger the privacy exposure.
In a best-case scenario, the number of distinct domains to which a web page connects should be only one, i.e. that of the remote server from which the web page was fetched.
The higher the number, the higher your are exposing yourself privacy-wise.
There is a good correlation between domains connected count and: undue page bloat, high privacy exposure, likelihood of being the target of data mining.
Example, a web page on http://www.ibtimes.com/ (which could be read all fine in all cases by the way):
| uBlock's mode | turned off | default settings | default-deny |
|---|---|---|---|
| domains connected |  |
|
 |
| privacy exposure | very high | medium | very low |
| bloat | ridiculously high | medium | very low |
And I had click-to-play enabled in all cases, i.e. it could have been worse (except for default-deny)...
The site-based switches allows to control uBlock's behavior on a per-site basis.
By default popups are allowed unless there is a filter to block them. When this setting is turned on, all popups will be unconditionally blocked for the current site, regardless of filters:
No popups for the current site: Try it
Blocking popups depends on whether the proper filters are present in the selected filter lists, so this feature is most useful for when a site creates popups for which there are no filter to take care of them in 3rd-party filter lists.
The second icon is to turn off strict blocking for the current site. By default strict blocking is on, this is the opposite of Adblock Plus.
As per ABP filter semantics, web pages themselves are never filtered, only secondary resources are subject to filtering.
So if you were to create a filter such as ||example.com^, and then navigate to https://example.com, Adblock Plus would not prevent you from connecting and loading the web page itself served at https://example.com, though all secondary resources pulled by that web page would be subjected to filtering.
uBlock respected that semantic until version 0.9.3.0. With version 0.9.3.0, uBlock will subject web pages themselves to filtering. This means that using the same test case above, uBlock will block the web page served by https://example.com -- as opposed to ABP:
Why the change? Because issue #1013 brought forth why it is desirable sometimes to block completely a web site, as opposed to what ABP-filtering semantic dictates.
In the end the chosen solution is to now have web page themselves subject to filtering just like all secondary resources.
In the figure above, a user will be given the choice to go back by closing the window or proceed to the web page by disabling strict blocking by any of the two options:
- Temporarily - The site will be temporarily allowed for a limited time (currently set at 60 seconds).
- Permanently - The site will be permanently allowed.
If the user disagree that a web page proper should be blocked (because of a false positive for example), then turning off strict blocking for the site...
No strict blocking for the current site.
... will prevent web pages proper for the site from being blocked by uBlock in the future: the filtering of the site will be done exactly as per ABP-filtering semantic, and just like with uBlock pre-0.9.3.0.
There are many benefits to strict blocking. For example, there is no good reason one should want to connect at all to any of the sites present in any one of the malware domain lists. Strict blocking will prevent this from happening.
I expect the need to disable strict blocking to be rather uncommon.
Important note: Keep in mind that when the above warning occurs, it doesn't necessarily mean the site is harmful, it just means that there is a matching filter in the selected filter lists. You decide whether the site is safe, and whether disabling strict blocking permanently for the site is appropriate.
You can easily toggle on/off cosmetic filtering for a given site:
No cosmetic filtering for the current site.
When present, the badge number indicates the number of elements which have been hidden on the page as a result of cosmetic filtering. If you disable cosmetic filtering while there are hidden elements on the page, these elements will become visible/hidden as you toggle off/on cosmetic filtering.
Cosmetic filtering is always enabled by default.
Tip: It is often suggested to use a static filter such as @@||example.com^$elemhide to prevent "adblock" detection by specific sites (example). You can accomplish the same thing more simply by just using toggling off cosmetic filtering using this switch while on the problematic site.