Adblock Plus and (a little) more
Do-Not-Track support in the experimental builds · 2011-10-04 20:50 by Wladimir Palant
Starting with Adblock Plus for Chrome 1.1.4.698 the experimental builds come with Do Not Track support that works the same as in Firefox. The current implementation isn’t the most efficient, this will be improved later.
Dropped support for old browser versions including Firefox 3.5 · 2011-10-04 10:59 by Wladimir Palant
Starting with Adblock Plus 1.3.11a.3172 old browser versions based on Gecko versions older than Gecko 1.9.2.13 will no longer be supported. This change is performed to simplify Adblock Plus code as well as to make regression testing easier again. This means in detail:
- Firefox 3.5 is no longer supported. Anybody still using it should update to a current Firefox version ASAP given that Firefox 3.5 is no longer supported by Mozilla and has known security issues. Similarly, Thunderbird 3.0 is no longer supported.
- Only reasonably recent Firefox 3.6.x releases are supported (Firefox 3.6.13 or newer). If you are running one of the older versions you should update ASAP, at least to Firefox 3.6.23 which is the current release on this branch. Similarly, users running Thunderbird 3.1.x need Thunderbird 3.1.7 or newer (preferably Thunderbird 3.1.9 which is the current release on this branch).
- Firefox Mobile 1.1 is no longer supported, at least Firefox Mobile 4.0 is required.
- SeaMonkey 2.0 is no longer supported, at least SeaMonkey 2.1 is required.
- Prism support has been removed. With Prism development no longer being continued the last release uses an outdated Gecko version.
- Songbird support has been removed. Even most current Songbird releases use an outdated and insecure Gecko version, so using Songbird’s browser component is not recommendable.
Experimental pop-up blocking support · 2011-10-03 16:29 by Wladimir Palant
The current development build (Adblock Plus 1.3.11a.3162) added support for blocking pop-ups directly, working for Gecko 1.9.2.6 (meaning Firefox 3.6.6) and higher. Filters will not block pop-ups by default, only if the $popup
type option is specified. So one can use the filter ||livejasmin.com^$popup
to block all pop-up windows opening livejasmin.com. Or one could use ||livejasmin.com^$popup,domain=example.com
to prevent only example.com from opening such pop-ups. Pop-ups opened by a page will appear in the list of blockable items and can be blocked from there.
For subscription authors: if you add pop-up blocking rules to your filter list you might want to do it in a backwards compatible way: ||livejasmin.com^$popup,image,~image
. This makes sure that the filter doesn’t block anything in Adblock Plus versions that don’t know the $popup
option.
Known issues:
- If the pop-up opens in a new window rather than a new tab you will briefly see the pop-up window. This window is closed before running any code
and sending any network requestshowever. Edit: The initial network request is actually being sent in this case but is canceled immediately after receiving HTTP headers. - For each pop-up opened you will see an additional
about:blank
entry in the list of blockable items. This is due to how Gecko works, a new window always loadsabout:blank
before loading the actual pop-up target. - For same-origin pop-ups (opening page and pop-up are from the same host) you will get only the
about:blank
entry. This is a Gecko limitation, so for such pop-ups you will only be able to block all pop-ups or none.
Introducing Eyeo GmbH, the company behind Adblock Plus · 2011-09-30 12:04 by Wladimir Palant
A few weeks ago we (meaning Till Faida and me) founded a new company called Eyeo GmbH (pronounced aɪ-o). Yesterday I got the official confirmation that all the formalities are done. This company will help us fund continued development of Adblock Plus now. My official title is “Managing director” now but don’t worry: I will continue doing what I’ve always done — lead Adblock Plus development and make sure that we have a great product to present. And Till will make sure that the business part works and we get money to put into the development (ok, that’s pretty much what he has been doing all along). And our community will hopefully continue being the great help it always was.
Improved experimental builds · 2011-09-29 11:50 by Wladimir Palant
The experimental development builds starting with Adblock Plus for Google Chrome 1.1.4.694 will disable the “old” blocking functionality now, only the new webRequest API will be used for blocking. This improves performance and memory use, it also makes sure that issues with dynamically loaded images no longer happen. I can only see one side-effect: blocked images are no longer collapsed, instead you will see a “broken image” placeholder.
Also, experimental builds will now appear as “Adblock Plus for Google Chrome (Beta) experimental build” in the extensions list, this way you can always check whether you are running the experimental or the “normal” build.
Automatic updates to Adblock Plus 1.3.10 temporarily disabled [Update] · 2011-09-29 07:49 by Wladimir Palant
Yesterday I asked Mozilla to put Adblock Plus 1.3.10 into the sandbox again to disable automatic updates. This is not because anything is wrong with Adblock Plus 1.3.10, it is actually because of a bug in Firefox 7 — updating the browser while an extension update is pending makes that extension disappear from the list. Mozilla promised a solution in the next few days at which point the automatic updates can be enabled again.
Experimental Adblock Plus for Chrome builds available with better blocking · 2011-09-28 19:20 by Wladimir Palant
Starting with Adblock Plus for Google Chrome 1.1.4.685 there are two development builds — the “standard” version and the experimental version. The experimental version uses the new webRequest
API that allows Adblock Plus to block requests better. Unfortunately, this API isn’t stable yet which means that you need to go to chrome://flags
and activate “Experimental Extension APIs” option. Then you will be able to install the experimental build and it will update to new experimental versions automatically.
What you should expect in this build:
- All ads blocked, no matter how fast the page loads.
- Background images and in-video ads will be blocked (feel free to uncheck “Block ads inside YouTube videos” option, it should no longer be required).
Known issues:
- Issues with sites loading images dynamically are not resolved yet, the old blocking mechanism is still active in these builds.
- Some false positives possible because Chrome doesn’t distinguish between objects and object subrequests.
Let us know if you see more issues with these builds.
Adblock Plus 1.3.10 released · 2011-09-28 10:23 by Wladimir Palant
Changes
- Added Latvian and Albanian translations.
- Fixed some minor issues.
- Some users will be asked to complete a survey about Adblock Plus.
Aktuelle Informationen der ukrainischen Botschaft? So findet man sie! · 2011-09-24 14:55 by Wladimir Palant
This is once again an off-topic blog post about the information policy of the Ukrainian embassy in Germany. Main point is making this information easier to find for Ukrainian citizens who live in Germany which is why it is being published in German and Russian.
Das ist jetzt mal ein Blog-Post, das rein gar nichts mit Adblock Plus zu tun hat. Sinn und Zweck ist lediglich, diese Informationen besser auffindbar zu machen.
Эта статья, в виде исключения, абсолютно не связана с Adblock Plus. Основной смысл ее публикации в том, чтобы эту информацию было немного проще найти.
Diagnostics 1.1.6 for Adblock Plus released · 2011-09-16 15:50 by Wladimir Palant
Diagnostics 1.1.6 has been released. This version only updates compatibility information, it is marked as compatible with all current application versions.