Adblock Plus and (a little) more
Adblock Plus 3.13 for Chrome, Firefox, Microsoft Edge and Opera · 2022-04-28 14:14 by Thomas Greiner
Install Adblock Plus 3.13 for Chrome
Install Adblock Plus 3.13 for Firefox
Install Adblock Plus 3.13 for Microsoft Edge
Install Adblock Plus 3.13 for Opera
This release contains substantial under-the-hood changes in preparation for making the extension compatible with Manifest v3 later this year, as well as additional features for extended element hiding filters. It also drops support for some old browser versions, namely Chromium 76 and Firefox 62.
User interface changes
- Developer tools panel no longer reflects changes to filters that were made elsewhere while it’s open (ui#1003).
- Filters added via Block element dialog will only be applied after the page is reloaded (ui#1031).
- Developer tools panel now also shows unmatched top-level frame requests (ui#1060).
- Fixed: Developer tools panel no longer suggests allowlist filters for snippet filters (ui#1023).
Filter changes
Started using eyeo’s Web Extension Ad Blocking Toolkit (release notes: 0.1.0, 0.1.1, 0.2.0, 0.2.1), which includes the following changes:
- Upgraded adblockpluscore to 0.6.0 (release notes: 0.5.0, 0.5.1, 0.6.0), which includes the following changes:
- Added support for
:has()alias for:-abp-has()to extended element hiding filters (core#229). - Added support for
:has-text()alias for:-abp-contains()to extended element hiding filters (core#229). - Added support for
:xpath()to extended element hiding filters (core#308). - Added support for
:not()to extended element hiding filters (core#369). - Reject filters that are too broad (core#264, ui#1063).
- Indicate which filter option is invalid (core#305).
- Various performance improvements.
- Various bug fixes.
- Added support for
- Fixed: Elements for blocked requests in about:blank frames aren’t hidden (ewe#152, ui#961).
- Fixed: Page-specific filters remained active after URL was rewritten (ewe#109, ui#1037).
Other changes
- Replaced adblockpluscore with EWE (ui#972, ui#998, ui#1021, ui#1060, ui#1097).
- Fixed: Messages from content scripts are ignored unless they are known to be safe (ui#1092).
Chromium-specific changes
- Dropped support for Chromium 76 and below (ui#1028).
This includes Chrome 76, Microsoft Edge 76 and Opera 63.
Firefox-specific changes
- Dropped support for Firefox 62 and below (ui#1028).
Known issues
- When navigating from a page where Adblock Plus is disabled to one where it’s enabled, the toolbar icon doesn’t change (ui#1120).
Comment [3]
Commenting is closed for this article.
Jason · 2022-05-15 01:06 · #
On Saturday, May 14th, the extension had stopped working. All filter lists including custom ones and any customization within the settings are gone. Not sure what happened. I had restarted the browser, added some lists, nothing is kept or in working order.
Reply from Thomas Greiner:
We have received some reports of that problem and are currently looking into the cause. Unfortunately, we’re unable to reproduce it on our end, so it would be great if you could help us out by sending more details (incl. browser version, extension version, settings) to support@adblockplus.org.
webmax · 2022-05-15 04:27 · #
Indeed, All filter lists including custom ones and any customization within the settings are gone. And the block add filters doesn’t work anymore
Reply from Thomas Greiner:
We have received some reports of that problem and are currently looking into the cause. Unfortunately, we’re unable to reproduce it on our end, so it would be great if you could help us out by sending more details (incl. browser version, extension version, settings) to support@adblockplus.org.
Danill · 2022-05-18 02:24 · #
Ditto Webmax’s description of the problem. Firefox 100.0.1 (64-bit) in permanent private browsing mode. Other extensions: Privacy Badger and DuckDuckGo Privacy Essentials.
Reply from Thomas Greiner:
Thank you for the additional pieces of information. Indeed, the problem appears to exist for those who use Firefox 100 and have the “Always use private browsing mode” setting enabled. Disabling that mode seems to restore all previous settings, so we’re currently working on a fix or a way to work around this problem.