-
Notifications
You must be signed in to change notification settings - Fork 436
Filter syntax extensions
This version of uBlock is no longer under development.
Consider using uBlock Origin or another adblocker.
uBlock Origin: https://github.com/gorhill/uBlock
Other adblockers and privacy tools:
Please note that donations sought on ublock.org are not benefiting uBlock Origin developers.
uBlock supports most of the Adblock Edge / Adblock Plus filter syntax. However uBlock does not support some very specific cases, and also has its own extensions added to the ABE/ABP filter syntax.
document:
Not supported. The purpose of the document option is to disable uBlock completely. The reason it is not supported is to be sure that users explicitly disable uBlock themselves if they wish (through whitelisting), and not have some external filter list decide for them.
uBlock extends Adblock Edge / Adblock Plus filter syntax.
important:
The filter option important means to ignore all exception filters (those prefixed with @@).
It applies only to net block filters. The important option will allow you to block with 100% certainty specific net requests.
Example 1: ||google-analytics.com^$important,third-party will block all net requests to google-analytics.com, disregarding any existing network exception filters.
Example 2: ||twitter.com^$important,third-party
inline-script:
To specifically disable inline script tags in a main page: ||example.com^$inline-script.
Entity-based cosmetic filters: Filters which are to be applied to a specific entity.
An entity is defined as follows: a formal domain name with the Public Suffix part replaced by a wildcard.
Example 1: google.* will apply to all similar Google domain names: google.com, google.com.br, google.ca, google.co.uk, etc.
Example 2: facebook.* will apply to all similar Facebook domain names: facebook.com, facebook.net.
Since the base domain name is used to derive the "entity", google.evil.biz would not match google.*.