Changes to parsing metadata from filter lists · 246 days ago by Sebastian Noack
Starting with Adblock Plus 3.4 (and developments builds as of 18.104.22.1685), special comments must be given at the top of the filter list, right below the header, otherwise they will be ignored. Furthermore, the
Checksum special comment is no longer supported.
Rewriting URL instead of blocking · 368 days ago by Hubert Figuière
Starting with Adblock Plus 3.2 for Chrome, Firefox and Opera (and development builds as of 22.214.171.1243), there is a new
$rewrite filter option to rewrite the URL of a resource instead of blocking it.
Internationalized domains in filters are now expected to be encoded as Punycode · 368 days ago by Sebastian Noack
Starting with Adblock Plus 3.2 (and development builds as of 126.96.36.1990), domains given in filters are expected to be encoded as Punycode.
Pre-configurable preferences for system administrators on Firefox 57 and above · 395 days ago by Sebastian Noack
Starting with Adblock Plus 3.1 and Firefox 57, system administrators will be able to pre-configure Adblock Plus in order to suppress the first run page or to add additional default subscriptions through a managed storage manifest. This feature is now available in the developments builds as of 188.8.131.528.
Added support for the $csp filter option · 395 days ago by Dave Barker
Starting with Adblock Plus 3.1 (and development builds as of 184.108.40.2068) the
$csp filter option is supported. The
$csp filter option allows for the injection of additional Content Security Policies.
Adblock Plus development builds for Firefox moved to new location · 423 days ago by Sebastian Noack
Mozilla is going to drop support for beta versions from AMO, which means we’ll need to go back to distributing the development builds of Adblock Plus for Firefox ourselves. Furthermore, Mozilla will force existing beta users to be automatically updated to the stable version. So if you want to keep using the development build of Adblock Plus for Firefox you’ll need to re-install it from it’s new location.
Web Extensions builds are now the official Adblock Plus for Firefox development builds · 635 days ago by Wladimir Palant
A while ago we announced our plan to migrate to the Web Extensions platform. With the current Firefox nightly builds being incompatible to classic add-ons already, we need to move a bit prematurely. So starting with Adblock Plus 220.127.116.114 development build, our development builds will be using the Web Extensions platform. If you are on Firefox 57, make sure to install the latest Adblock Plus development build and it will be working again.
New #?# syntax for advanced element hiding rules · 701 days ago by Hubert Figuière
Starting with Adblock Plus 1.13.3 for Chrome and Opera (and development builds as of 18.104.22.1682) there is a new and improved syntax which can be used for advanced element hiding filters. It allows for elements to be hidden based upon their contents using
:-abp-has. CSS property filters have also being adjusted to be consistent with the new syntax, so both those and
:-abp-has filters now use the
#?# option separator.
Fixing Adblock Plus 2.9 for Thunderbird and SeaMonkey users · 719 days ago by Wladimir Palant
Adblock Plus 2.9 introduced very significant changes to the data storage. The unfortunate side-effect was that Adblock Plus was broken for Thunderbird users as well as users on pre-release SeaMonkey versions, and nobody noticed before the release. After we discovered a problem with our original fix, as of Adblock Plus 22.214.171.12451-beta development build things should work correctly on all platforms. This being a rather non-trivial change, your feedback is appreciated. If no other issues pop up we plan to release Adblock Plus 2.9.1 next Tuesday, June 6.
New filter type option for WebRTC connections · 769 days ago by Dave Barker
Starting with Adblock Plus 1.13.3 for Chrome and Opera (and development builds as of 126.96.36.1991) the blocking of WebRTC connections is supported. Those connections will have the new request type of “webrtc” and so filters can be made to target them by adding the
$webrtc type option.
WebRTC is an experimental browser technology which is supposed to be used for things like video conferencing. Unfortunately despite still being in active development it’s already being misused to serve adverts! Since Chrome does not yet allow WebRTC connections to be blocked by extensions directly (Chromium issue 707683), we’ve had to implement a workaround to achieve this.
Support for other platforms such as Firefox should follow soon, we’ll keep you posted.