Introduction to Adblock edge filters
The options described in this section should be enough for users who have to create a filter occasionally.
Basic filter rules
The most trivial filter you can define is of course the address of banner you want to block. However, often this address changes every time you open a page. For example it could be
http://example.com/ads/banner123.gif where 123 is a random number. Here blocking the complete address won't help you, you need a more general filter — like
http://example.com/ads/banner*.gif##. Or maybe even http://example.com/ads/*##.
Note: Make sure that you are not replacing too much by wildcards. The filter
http://example.com/* will definitely block all banners but it will also block everything else from example.com that you still might want to see.
Defining exception rules
Sometimes you will notice that one of your filters that is usually working quite well blocks in some case blocks something that it shouldn't be blocking. You don't want to remove this filter but you still don't want it to match in this one case.
That's what exception rules are good for — they allow you to define cases where filters shouldn't be applied. For example if you are unhappy with your filter
http://example.com/advice.html##, you can define an exception rule @@advice
. Exception rules are no different from filter rules, you can use wildcards or regular expressions. You only have to precede them by @@
to indicate an exception rule.
Exception rules can do more. If an exception rule starts with http: or https: (optionally with a pipe before it) it will make whole pages an exception. For example, if your exception rule is
@@|http://example.com and you open some page from example.com — Adblock edge will be entirely disabled on this page and nothing will be blocked.
Matching at beginning/end of an address
Usually Adblock edge treats every filter as if it had a wildcard at its beginning and end, e.g. there is not difference between the filters
*ad*. While this is usually unproblematic, sometimes you wish that the filter you defined only matches at the beginning or end of an address. For example you might want to block all Flash, but if you add the filter
swf the address
http://example.com/swf/index.html will also be blocked.
Solution to this problem: add a pipe symbol to the filter to show that there should be definitely the end of the address at this point. For example the filter
swf| will block
http://example.com/annoyingflash.swf but not
http://example.com/swf/index.html##. And the filter |http://baddomain.example/
will block http://baddomain.example/banner.gif
but not http://gooddomain.example/analyze?http://baddomain.example##.
Sometimes one wants to block
http://example.com/banner.gif as well as
http://www.example.com/banner.gif##. This can be achieved by putting two pipe symbols in front of the filter which makes sure the filter matches at the beginning of the domain name: ||example.com/banner.gif
will block all these addresses while not blocking http://badexample.com/banner.gif
(requires Adblock edge 1.1 or higher).
Marking separator characters
Often you need to accept any separator character in a filter. For example, you might write a filter that blocks
http://example.com:8000/ but not
http://example.com.ar/##. Here the symbol ^ can be used as a placeholder for a single separator character: http://example.com^
(requires Adblock edge 1.1 or higher).
Separator character is anything but a letter, a digit, or one of the following: _ - . %. The end of the address is also accepted as separator. In the following example all separator characters are shown in red: http://example.com:8000/foo.bar?a=12&b=%D1%82%D0%B5%D1%81%D1%82. So this address can be blocked with the filter
Any rule that starts with an exclamation mark is considered a comment. It will still show up in the filter list but in grey instead of black. Adblock edge will ignore this rule for actual blocking so it is safe to write there whatever you want. You can place a comment rule above a real filter to describe what it is doing. Or you can put a comment on top of your filter list stating your authorship (most filter list authors do that).
The features described in this section are usually used only by power users and filterlist creators. Feel free to skip it.
Specifying filter options
Adblock edge allows you to specify a number of options to modify the behavior of a filter. You list these options separated with commas after a dollar sign ($) at the end of the filter, for example:
*/ads/* is the actual filter and
match-case are its options. Currently the following options are supported:
- Type options: determine which types of elements a filter can block (or whitelist in case of an exception rule). Multiple type options can be specified to indicate that the filter should be applied to several types of elements. Possible types are:
script — external scripts loaded via HTML script tag
image — regular images, typically loaded via HTML img tag
background — background images, often specified via CSS
stylesheet — external CSS stylesheet files
object — content handled by browser plugins, e.g. Flash or Java
xbl — XBL bindings (typically loaded by
-moz-binding CSS property)
ping — http://weblogs.mozillazine.org/darin/archives/009594.html link pings
xmlhttprequest — requests started by the http://www.w3.org/TR/XMLHttpRequest/ XMLHttpRequest object
object-subrequest — requests started plugins like Flash
dtd — DTD files loaded by XML documents
subdocument — embedded pages, usually included via HTML frames
document — the page itself (only #whitelist exception rules can be applied to the page)
elemhide — for exception rules only, similar to
document but only disables #elemhide element hiding rules on the page rather than all filter rules (Adblock edge 1.2 and higher required)
other — types of requests not covered in the list above
- Inverse type options: specify the element types the filter should not be applied to. Possible inverse type options:
- Restriction to third-party/first-party requests: If the
third-party option is specified, the filter is only applied to requests from a different origin than the currently viewed page. Similarly,
third-party restricts the filter to requests from the same origin as the currently viewed page.
- Domain restrictions: The option
domain=example.com means that the filter should only be applied on pages from "example.com" domain. Multiple domains can be specified using "|" as separator: with the option
domain=example.com|example.net the filter will only be applied on pages from "example.com" or "example.net" domains. If a domain name is preceded with "", the filter should not be applied on pages from this domain. For example,
domain=example.com means that the filter should be applied on pages from any domain but "example.com" and
domain=example.com|foo.example.com restricts the filter to the "example.com" domain with the exception of "foo.example.com" subdomain.
match-case — makes the filter only apply to addresses with matching letter case, e.g. the filter
*/BannerAd.gif$match-case will block
http://example.com/BannerAd.gif but not
— this option will override the global "Hide placeholders of blocked elements" option and make sure the filter always hides the element. Similarly the collapse
option will make sure the filter never hides the element.
— for any address matching a blocking rule with this option and not matching any exception rules with this option a http://donottrack.us/ Do-Not-Track header will be sent (requires Adblock edge 1.3.5 or higher). For backwards compatibility it is recommended to use this option in combination with contradicting type options, this will prevent this filter from blocking anything in earlier Adblock edge versions: *$donottrack,image,image##
Using regular expressions
If you want even more control about what your filters match and what they don't match, you can use regular expressions. For example the filter
/banner\d+/ will match
banner321 but not
Note: For performance reasons it is recommended not to use regular expressions if they can be avoided.
Sometimes you will find advertisements that can't be blocked because they are embedded as text in the web page itself. If you look at the source code of the web page you might find something like this:
<div class="textad">---Cheapest tofu, only here and now!---</div>---<div id="sponsorad">---Really cheap tofu, click here!---</div>---<textad>---Only here you get the best tofu!---</textad>---
You need to download the web page so you will necessarily download the advertisements. All you can do here is to hide the advertisement so you don't need to see it. That's what element hiding is meant for.
The first advertisement above is contained inside a div element with class attribute "textad". The following rule will hide exactly this combination:
marks an element hiding rule while the rest is a selector identifying the elements that need to be hidden. You can hide elements by their id attribute similarly,
div#sponsorad will hide the second advertisement. You don't need to specify the element name, the rule
will work just as well. And you can hide elements by element name only, e.g.
for the third advertisement.
The http://adblockplus.org/en/elemhidehelper Element Hiding Helper extension helps selecting the correct element and writing the corresponding rule without having to view the source code of the page. Basic HTML knowledge is useful nevertheless.
Note: Element hiding works very differently from normal filters. This has the implication that no wildcards are supported in element hiding rules.
Limiting rules to certain domains
Usually you want to hide a specific ad on one specific site, you don't want your rule to be applied on other sites. For example the rule
might hide valid code on some sites. But if you write it as
it will be applied on http://example.com/
but not on http://example.org/##. You can also specify multiple domains — simply separate them with commas:
If a domain name is preceded with "", the rule will not be applied on pages from this domain (requires Adblock edge 1.1 or higher). For example,
will be be applied on pages from any domain but "example.com" and example.com,foo.example.com
*.sponsor makes the rule apply on "example.com" domain with the exception of "foo.example.com" subdomain.
Note: Due to the way how element hiding is implemented, you really can only limit it to full domain names. You cannot use any other part of the address and you cannot use
domain as a replacement for
Note: Element hiding rules with domain limitation can be used to hide browser's user interface elements as well. For example the filter rule
Some advertisers don't make it easy for you — their text advertisements have neither an id nor a class attribute. You can use other attributes to hide those, for example
will hide tables with width attribute set to 80%. If you don't want to specify the full value of the attribute,
will hide all div elements with title attribute containing the string "adv". You can also check the beginning and the end of an attribute, for example
will hide div elements with title starting with "adv" and ending with "ert". As you see, you can also use multiple conditions —
table[width="80%"][bgcolor="white"] will match tables with width attribute set to 80% and bgcolor attribute set to white.
In general, any CSS selector supported by Firefox can be used for element hiding. For example the following rule will hide anything following a div element with class "adheader":
. For a full list of CSS list see http://www.w3.org/TR/css3-selectors/ W3C CSS specification (note that not all selectors are supported by Firefox yet).
div.adheader + *
Simplified element hiding syntax
Adblock edge supports simplified element hiding syntax (e.g.
#div(id=foo)) for backwards compatibility only. Using this syntax is discouraged, usual CSS selectors are preferred. Support for this syntax might be removed at some point.