github AdguardTeam/AdguardBrowserExtension v2.3.8
2.3.8

latest releases: v4.3.35, v4.3.35-beta, v4.3.31...
7 years ago

This release contains a lot of changes and bugfixes in Adguard core code, so it will influence all browsers.

Here is what's new in version 2.3.8

Core

[Added] Annoyances filter: https://blog.adguard.com/en/adguard-news/annoyances-filter.html

This filter blocks irritating elements on webpages, including cookie notices, third-party widgets and in-page popups (Doesn’t include social media widgets and buttons, to block them you can still use Social media filter separately). It was inspired by Fanboy Annoyances List, but doesn’t duplicate it, so you can use them both together.

[Added] New "Assistant" UI: #184
[Added] Assistant core code refactoring. We've reworked the whole Assistant module in order for it to be reused in other Adguard products. For instance, the same code is used in Adguard for iOS manual element blocking feature.
[Fixed] An issue with creating an invalid rule: #122

Microsoft Edge

Edge extension has finally arrived! We still cannot publish it on Windows Store as this feature just is not available for common developers. So, to install Adguard you should make some changes to your Edge configuration.

Minimum supported Edge version is 38.14352.1002.0.
This means that you should be on Insider Preview Windows version.

  1. Go to "about:flags" page.
  2. Turn on "Enable extension developer features".
  3. Unpack edge extension archive.
  4. Open Edge settings -> Extensions.
  5. Click "Load extension" button and choose unpacked extension folder.
  6. That's it, I hope you'll like it!

Known issues:

  1. Integration mode is not working yet.
  2. "Export" function crashes Edge.
  3. Adguard browser menu looks bad as we cannot control menu container size and shape.

Chromium

[Added] Blocking WebSocket connections: #203
[Changed] Code for chromium extension was massively refactored in order to port our extension to Microsoft Edge browser: #202
[Changed] Adguard now stores filters using chromium storage API instead of the file system like we did earlier. This has finally resolved all compatibility issues we had with CCleaner: #253
[Fixed] Gmail.com tabs become irresponsive after cancelling selector menu: #248

Firefox

[Fixed] Wrong filter rules count in FF add-on: #214
[Fixed] PaleMoon menu is blacked out in integration mode: #92

Safari

Content blocking API issues

[Fixed] Wrong rules are constructed for website with non-standard port: #236
[Fixed] Safari doesn't support content-blocking rule with regexp, which contains negative lookahead: #231

Old API issues

[Fixed] Performance issues with the old API: #251
[Fixed] Safari extension with old API blocks the same image multiple times: #246

Other changes

[Changed] When both 'Blocked' and 'Whitelist' checkboxes are selected, the log should display Blocked+Whitelisted requests: #35
[Fixed] Turn off caching for requests downloading filter updates: #235
[Fixed] XMLDocument can be a valid HTML document: #233
[Fixed] Enabling 'Use optimized filters' distorts filter count: #230
[Fixed] Wrong preview is shown while blocking elements on yandex.ru: #200
[Fixed] Wrong area selection shown on yandex.ru: #191
[Fixed] $genericblock modifier does not work properly: #188
[Fixed] Selector border position is wrong (below the actually selected element): #187

Don't miss a new AdguardBrowserExtension release

NewReleases is sending notifications on new releases.