A long time has passed since the last release. But we weren't sitting on our hands. We fixed a whole lot of various bugs, so most users will find something positive in this update. This version also contains some sweet additions that will be interesting mostly for rule creators.

[Improved] $important modifier was added to the rule constructor: #626

This one is a rather obvious: when you use the manual blocking tool to create a rule, you can now give this rule a higher priority by ticking the checkbox. The `$important` modifier was available before, but you had to manually add it via the user filter.

[Added] $csp modifier support: #685

This is strictly for the rule creators, as it requires the basic understanding of the Content Security Policy security layer.

This modifier completely changes the rule behaviour. If it is applied to a rule, it will not block the matching request. The response headers are going to be modified instead.

You can find the syntax and examples for `csp` inside the issue.

Refactoring

We had been waiting for this for a long time, it took a lot of time but now the code is much more simple and convenient to work with.

Build process

The builds themselves are now available directly on GitHub, all the updates will be stored here. The build names are now more clear and understandable.

All additions, improvements and issues fixed in this release:

Common

• [Added] `$empty` modifier: #280
• [Added] Adguard French filter: #612
• [Added] “Select all/none” buttons to rules constructor: #703
• [Changed] '2016' to '2017': #519
• [Changed] filterlists.com were added to possible filters sources: #544
• [Changed] Filtering log performance: #403
• [Fixed] Rule constructor can't create a rule with
• [onclick] attribute which contains a big script: #469
• [Fixed] Rule constructor works incorrectly with TD tag: #483
• [Fixed] Regular expressions with `$` aren't processed properly: #517
• [Fixed] Error while parsing rules with `$replace` modifier: #559
• [Fixed] Error while parsing wide filtering rules: #556
• [Fixed] Basic URL rule, which contains domain name, blocks WS: #528
• [Fixed] Blocked `blob:` URLs #525
• [Fixed] Errors while parsing CSS rules: #617
• [Fixed] Sustainability to the LastPass vulnerability: #625
• [Fixed] Huge user filter slows down the 'options' page loading: #641
• [Fixed] Browsing security doesn't work: #580
• [Fixed] Error parsing pseudo class: #576
• [Improved] WebRTC circumvention: #588
• [Improved] Separate loading of the cosmetic filters and JS filters: #512
• [Changed] German translation was updated: #680
• [Changed] A link for "Protected by Adguard for Windows" menu item was added to the description page: #672
• [Fixed] Adguard settings window is not shown in private mode: #658
• [Fixed] WebRTC circumvention: #588
• [Fixed] Adguard 2.6.1 Beta does not block WebSocket connection: #652
• [Fixed] Auto-activation of filters still work in integration mode: #666
• [Fixed] `$webrtc` does not work on rapidvideo.com: #669
• [Fixed] Filtering log errors: #687
• [Fixed] A bug with element hiding rule with domains containing www: #665
• [Fixed] A rule with a single `$content` modifier now will be ignored. A rule with multiple modifiers which includes `$content` continue to work: #719
• [Fixed] CSP and WebRTC rules are now processing the proper way: #725
• [Fixed] unutulmazfilmler.co - blocked iframe is not collapsed: #733
• [Fixed] $content modifier works as URL exclusion: #719
• [Fixed] Difference of blocked ads before AG turn off and after turn on: #748

Firefox

There are few notable changes in this release that take place in Firefox version. First of all, FF have finally released the WebExtensions technology which allowed us to completely revamp the extension code. It now greatly resembles the code for Chrome extension, which makes it much easier for further development among other advantages. A lot of other improvements have been done, too.

• [Improved] FF extension migrated to WebExtensions: #523
• [Improved] "Require" calls were got rid of: #367
• [Improved] SDK is not being used anymore: #151
• [Improved] `-moz-binding` approach was got rid of: #463
• [Fixed] Errors in FF browser console: #673
• [Fixed] Cleaning Firefox data breaks Adguard extension: #681
• [Fixed] Filtering log: new tab stays in the background when opened: #697
• [Fixed] Scrollbar is missing in the filtering log: #732

Firefox - other

• [Fixed] Integration mode: #607
• [Fixed] Possible error with generichide implementation: #574

Chromium

• [Fixed] `chrome.webRequest.onBeforeRequest` now intercepts WebSocket: #572
• [Improved] Text in the rules constructor is too dark with built-in dark theme for dev tools: #739
• [Fixed] Separators in rules constructor are collapsed in some cases: #741

Edge

• [Fixed] Edge Storage size limit issue: #566
• [Fixed] Russian localization: #538
• [Fixed] Error on start/adding/removing filter subscription: #627
• [Fixed] Browsing security - "Proceed anyway" issue: #628
• [Improved] CSP fix is now applied for newer Edge versions (Insider Preview): #602
• [Improved] Edge extension now downloads own platform filters: #721
• [Fixed] Edge `browser.windows.getAll` issue in the Insider Fast ring build: #569
• [Fixed] Adguard dropdown menu glitch - Edge browser: #675
• [Fixed] Advanced settings menu does not expand: #708
• [Fixed] "Block ads on this website" tool misbehaves: #691
• [Fixed] Google Docs document glitch: #720

Safari

• [Changed] "Activate the most appropriate filters automatically" setting is now disabled by default: #715
• [Fixed] `$websocket` modifier works incorrectly in Safari: #597
• [Fixed] Possible websockets blocking issue: #586
• [Fixed] `$elemhide` exceptions also affect basic rules: #642
• [Fixed] User filter rules are being imported from .txt together with comments: #584
• [Fixed] Browsing security error: #583
• [Fixed] Safari tab / Ergonomics issue: #505
• [Fixed] "Block ads on this website" tool does not work in Safari 9.1.3: #704