New data storage in Adblock Plus for Firefox · 2017-04-11 11:42 by Wladimir Palant
As of Firefox 57, classic extensions such as the current Adblock Plus for Firefox will no longer load and only Web Extensions will be allowed to continue working. In order to prepare for the transition, starting with Adblock Plus 22.214.171.12444 development build we will use Web Extensions for data storage. Any existing data (this includes both current filters/subscriptions and automatic backups) will be taken over automatically and ideally there should be no visible changes at this point. However, the data will no longer be stored in the
adblockplus/patterns.ini file of your Firefox profile but rather in the
Please tell us about any data loss issues you encounter after this change. We are moving towards releasing Adblock Plus 2.9 which will start data migration for our entire user base. Note that the format of the Web Extensions storage is still supposed to change which will hopefully make it more robust and performant.
CSS property matching improvements · 2016-11-14 13:05 by Felix Dahlke
About a year ago, we introduced CSS property filters as a means of hiding elements based on their styles. Today, we have landed two improvements to this:
Case insensitive matching
This is a change in semantics; CSS properties will now always be matched in a case insensitive manner, to make it consistent with the way Adblock Plus matches URLs. This is unlikely to result in undesired behaviour as there shouldn’t be many use cases for case sensitive property matching.
Regular expression matching
Until now, CSS properties could only be matched using the simple URL matching syntax, which made it difficult to match property values in a fine-grained manner. To address this, properties can now optionally be matched using regular expressions. The default matching behaviour is still the same, to use regular expressions, a matching expression needs to start and end with
/, for example:
These improvements are available in Adblock Plus for Firefox as of 126.96.36.19929 and Adblock Plus for Chrome and Opera as of 188.8.131.522, and will presumably be released with the next stable version on each platform respectively.
Please note that we still consider CSS property filters an experimental feature, and therefore subject to change. Considering this, and the fact that CSS property filters are slower than regular element hiding rules, they should only be used as a last resort.
New development build of Adblock Plus for Internet Explorer is available · 2016-10-19 10:17 by Oleksandr Paraska
A new development build of Adblock Plus for Internet Explorer is finally available. The most important change in this version is the change to the element hiding functionality. As of this version on IE10+ the element hiding will be done in a similar way as in our other extensions.
New element hiding approach in Firefox · 2016-10-10 15:46 by Wladimir Palant
Traditionally, element hiding on Firefox worked quite differently from all other platforms supported by Adblock Plus. Rather than decide on the filters for each website individually, all element hiding rules would be written into a single
elemhide.css stylesheet file that would apply to all websites unconditionally. This approach had a few disadvantages:
- The global stylesheet could not consider exceptions, such as websites where a particular rule should not apply — we had to implement a complicated mechanism to make sure that the rule didn’t have any effect in such cases, and on some websites there still were side-effects.
- Changing a single element hiding rule caused the global stylesheet to apply again to all open tabs, this could cause significant delays.
- With multiprocess Firefox coming up and sandboxing enabled on some platforms, we could no longer rely on being able to access that file.
Luckily, Firefox implemented better mechanisms to apply stylesheets to documents a while ago and as of Adblock Plus 184.108.40.20606-beta development build we are now taking full advantage of these. We will now make a separate decision for each website, which (if any) element hiding rules should apply. And we don’t sacrifice performance for that because the majority of element hiding rules will go into a preloaded stylesheet with all the rules which apply unconditionally.
There are a few drawbacks here:
- New element hiding rules will no longer apply immediately, just like blocking rules they now require the document to be reloaded (can actually be seen as a good thing because consistent). This also affects Element Hiding Helper extension which will need to be updated.
- We are no longer able to count hits for element hiding exception rules (issue 4509). We simply don’t know any more whether the rule that the exception applies to would have matched anything.
- Element hiding rules apply with a slight delay which in theory might cause some ads being shown and then flashing out. In practice, I haven’t seen this yet.
This is a huge change to the inner workings of Adblock Plus and while we tested it quite thoroughly some issues are expected — let us know if you notice any.
New filter type option for WebSockets · 2016-09-21 14:30 by Wladimir Palant
Starting with Adblock Plus 1.12.2 for Chrome, Opera and Safari we can block connections initiated via WebSockets on all major platforms (this functionality was available on Firefox since the very start). However, we didn’t have a special type for these requests as these were listed with type “other” instead. The assumption was that the protocol
wss:// would be sufficient for filter list authors in order to target WebSocket connections specifically. However, we received feedback that this wasn’t the case.
So with the current development builds (Adblock Plus 220.127.116.1102 for Firefox and Adblock Plus 18.104.22.1685 for Google Chrome, Opera and Safari) WebSocket connections are listed with the new type “websocket.” Consequently, filters can be made to target such connections specifically by adding
$websocket type option. Existing filters will have to be duplicated for now:
This syntax will support both new and old Adblock Plus versions as long as the versions without support for the “websocket” type are still common (these will ignore the first filter).
Edit (2016-09-22): This post was originally suggesting specifying both
other options on one filter. This approach will not work in Adblock Plus versions without support for the
websocket option because filters with unknown options are ignored.
Experimental Safari Content Blocking support · 2016-05-18 14:54 by Dave Barker
With Safari 9 Apple announced support for Content Blocking Extensions, with the aim of providing a more efficient way for Safari extensions to block adverts. (At the same time they announced the depreciation of the old method Safari extensions use to block adverts, implying it is likely to be removed from future Safari versions.) Since then we have been working on adding experimental Content Blocking support to Adblock Plus (issue 3687). It will be available as of Adblock Plus 1.12 for Safari and is now in the developments builds as of 22.214.171.1242.
Content Blocking can be enabled from the options page for supported versions of Adblock Plus and Safari:
But wait! Before you give it a try, here are some things you should know:
- Safari disables the old method we use to block adverts when Content Blocking is enabled. This means that after disabling Content Blocking you will need to restart Safari.
- To support Content Blocking we translate Adblock Plus filters to Content Blocking rules. While we’re working to improve this it is still a fairly slow process, you may notice a small delay when enabling Content Blocking or when adjusting your filters and subscriptions. (Each change causes the Content Blocking rules to be regenerated.)
- Adblock Plus filters do not translate perfectly to Content Blocking rules, which means that some filters simply won’t work at all and some other filters may not work exactly as before.
- Safari 9 has a limit of 50,000 Content Blocking rules, causing an error to be shown when exceeded: “Extension compilation failed: Too many rules in JSON array.”. If you see this error try disabling some filter list subscriptions. We are working to further compress the Content Blocking rules generated and also hope that Apple will increase this limit in future versions of Safari.
“Block element” dialog now displayed as a popup window · 2016-02-18 17:14 by Dave Barker
We’ve been working on some changes to the “Block element” feature. These changes will be available in Adblock Plus 1.11 for Chrome, Opera and Safari and now in development builds as of 126.96.36.1994.
The “Block element” feature allows you to select elements on the current page and generate filters to block them. After selecting an element the “Block element” dialog is displayed which allows you to confirm the filters that should be added. For Chrome and Opera this dialog is now displayed as a popup window (issue 2426) instead of as part of the website itself. In Safari the dialog will open as a new tab instead. (This is because Safari unfortunately doesn’t provide an equivalent way for us to open popup windows.)
This change should resolve a number of issues with the “Block element” dialog, most importantly one that was being used by websites to reliably detect if Adblock Plus was installed.
Bringing "blockable items" to Chrome, introducing the Adblock Plus developer tools panel · 2016-02-03 18:08 by Sebastian Noack
Since we ported Adblock Plus to Chrome, we promised our users feature-parity with Adblock Plus for Firefox. While we are still not there, the probably most significant feature that has been missing on Chrome for a long time – but not anymore – is a way to view blockable items/requests along with applied filters.
For Chrome and Opera, we decided to implement “blockable items” as a developer tools panel (issue 154). Being a tool for advanced users, filter list authors and our own developers, we think that it belongs there. And integrating it with the developer tools gives a nice user experience.
The developer tools panel is now available in the development builds as of Adblock Plus 188.8.131.523 for Chrome and Opera, and will be included in the next release, Adblock Plus 1.11. In order to use the developer tools panel, inspect the current page (
Ctrl + Shift + I) and click on the “Adblock Plus” panel. Unfortunately, Chrome currently doesn’t provide a way to open the developer tools panel programmatically, e.g. from our icon menu.
Also as opposed to “blockable items” on Firefox, we don’t record items in advance, to avoid performance penalties and additional memory usage while not using the developer tools panel. Therefore you have to (re)load the page, with the panel open, to see all items.
The items shown in the developer tools panel include:
- Web requests as seen by Adblock Plus. Blocked/Whitelisted requests are indicated red/green, with the responsible filter given in the right column. When moving the mouse over a request item, buttons – to block or whitelist the request – appear.
- Element hiding filters that match and hide any element on the current page. However, since Chrome doesn’t provide a way to detect actual element hiding hits, these items are simulated by observing the document for hidden elements that match the selector of any active element hiding filter, which might not give completely accurate results in rare situations.
- Document-based whitelisting including
ELEMHIDE, GENERICBLOCK and GENERICHIDE exception rules, that apply for any document on the current page. Note that if a
DOCUMENTexception rule applies, there won’t show any further items – as it pretty much disables Adblock Plus – for that document.
Finished support for multi-process Firefox · 2016-01-11 12:58 by Wladimir Palant
We continued working on improving our support for multi-process Firefox. So far we have still been relying on backwards compatibility code in Firefox which is slow and error-prone. However, starting with Adblock Plus 184.108.40.20623-beta development build that backwards compatibility code no longer applies to Adblock Plus — now we are on our own. As far as I know, all issues have been resolved, with one exception:
- Element hiding functionality isn’t working on Mac OS X when multi-process is enabled (bug 1187099). Mozilla is fixing this, we might also implement our own workaround however.
This development build is a release candidate for Adblock Plus 2.7.1 which we plan to release on January 19, 2016. Please tell us if you notice any other issues, particularly around Blockable items list and Issue reporter.
Reintroducing the $ping filter option · 2015-12-23 16:59 by Sebastian Noack
Historically, there has been the
$ping filter option in Adblock Plus, to limit request blocking filters to the URL given by the ping attribute on links. When such a link is clicked, the browser sends a request to that URL in the background. This technique is mostly useful for tracking. However, it has never been enabled by default in Firefox. Therefore, with Adblock Plus 2.0,
$ping got deprecated and merged into
ping HTML attribute. And it is enabled by default. Moreover, on Chrome,
<a ping> is supported by default too. And starting with Chrome 49, it’s possible to distinguish these requests from others.
Therefore, we are reintroducing the
$ping filter option (issue 3452). Starting with Adblock Plus 220.127.116.1199 for Firefox and 18.104.22.1688 for Chrome/Opera, filters using the
$ping option will only match requests that are either caused by
<a ping> or by
navigator.sendBeacon(). Note that the filter option
$other won’t match these requests anymore.