Browser-extension Release - AdGuard sürümleri

AdGuard Tarayıcı eklentisi
sürüm 3.2.1 3 Temmuz 2019 tarihinden

Your average grocery list is probably longer than this update’s changelog, but don’t let it fool you. We introduce two powerful new tools that are going to serve well to filtering rules creators and will noticeably improve the ad blocking quality.

[Added] Scriptlets support #1366

Scriptlets is a powerful ad blocking instrument. You can say that scriptlet is an internal script (a mini-program) that we install in the extension, and then execute that script with the help of filtering rules. Putting it simply, scriptlets allow us to modify how the code of the web page behaves. As for the practical use, this helps to block anti-ad blockers, for example.

[Added] $redirect and $rewrite modifiers support #1367

They are practically the same modifiers, and they allow to substitute resources. If you are not a custom filtering rules aficionado, don't bother with it. Just know that it is yet another instrument in the hands of filter developers that helps efficiently block ads.

We should mention that both $redirect and $rewrite modifiers are still kind of working in test mode, but they are fully operational and you should feel free to use them.

  • [Changed] The browser action UI on internal browser pages #1433
  • [Changed] Manifest file has been updated #1419
  • [Fixed] CSS rules exceptions don't work #1412
  • [Fixed] "Allow search ads and websites' self-promotion" checkbox doesn't correlate properly with "Self-promotion" filter #1287
  • [Improved] uBlock Origin syntax recognition #1383, #1428
AdGuard Tarayıcı eklentisi
sürüm 3.0.13 16 Nisan 2019 tarihinden

After a series of hasty hotfixes we are happy to finally do a full-scale release. It may be not the biggest AdGuard browser extension release of all times, but it’s something. Inside you will find some small-ish changes and of course more bug fixes! This time, they were not so urgent, though.

  • Changed] "Mobile ads filter" is enabled by default on the Firefox for Android #1307
  • [Changed] $badfilter collection passed to ReplaceFilter #1340
  • [Changed] Chinese date format is now used for filters' update time in Chinese interface #1322
  • [Changed] Manifest file now properly indicates the latest supported Chrome version #1134
  • [Fixed] "Add custom filter" button is shown in English after adding a custom filter #1356
  • [Fixed] "Remove X-Client-Data header" has been made specific to Google Chrome only #1362
  • [Fixed] “Thank you” page in Edge #1369
  • [Fixed] $stealth modifier does not work in some cases #1342
  • [Fixed] BODY tag is ignored in the rules constructor in developer tools #1301
  • [Fixed] Comment symbol ! is applied as a URL blocking rule #1361
  • [Fixed] Enabled filters in turned off filter groups should be updated after the group is turned back on #1334
  • [Fixed] Incorrect automatic activation of the language-specific filters #1354
  • [Fixed] Language-specific filters are automatically activated even if the Language-specific filter group is disabled #1308
  • [Fixed] Last custom filters update check time is not saved #1347
  • [Fixed] Settings page in the extension doesn't wait until the extension is initialized before requesting information #1329
  • [Fixed] Standalone server breaks the extension's popup #1343
  • [Fixed] Strings alignment on the Settings screen #1360
  • [Fixed] The extension doesn't subscribe to the abp:subscribe - type links in the iframe #1357
AdGuard Tarayıcı eklentisi
sürüm 3.0.11 2 Nisan 2019 tarihinden
Sorry for another hotfix. It appeared, that filter lists updates were broken since v3.0 first release for those who restart their browser too often. This update fixes #1346and #1331.
AdGuard Tarayıcı eklentisi
sürüm 3.0.10 21 Mart 2019 tarihinden

Turned out, we overlooked a couple of minor bugs and inconsistencies in the previous hotfix. Here's a quick fix to set things right.

[Fixed] Statistics flushed after browser restart (randomly) #1341
[Fixed] ExtCss DOM observer fails in Edge due to a "Syntax error" #1330
[Fixed] Extension doesn't search for other rules if first found rule matched with badfilter rule #1328
[Fixed] User filter editor is often stuck in "Saving" state #1316
[Fixed] AdGuard extension does not properly show on Chrome 56 (winXP) #1315
[Fixed] AdGuard extension doesn't work in UC browser #1318
[Fixed] ExtendedCss recursively calls MutationObserver #1317

AdGuard Tarayıcı eklentisi
sürüm 3.0.8 7 Mart 2019 tarihinden

As they say, you can't have a good release without a hotfix. Or maybe they don't say that, but we sure need one.

In this update, we fix a particularly nasty bug that causes high CPU load because of some filtering rules.

AdGuard Tarayıcı eklentisi
sürüm 3.0.7 6 Mart 2019 tarihinden

New AdGuard Browser Extension follows the trends. As if ads were not bad enough, the web today is teeming with trackers. Big companies want to know everything about you, and AdGuard is here to stop it. The new Stealth Mode is designed specifically to protect your online privacy — an entire new module dedicated just for that. But that’s even not the first thing you will notice. Of course, the new design will steal the show. Let’s have a closer look.

[Improved] Renewed design

Fresh icon and menu designs that make interface more natural and user-friendly, with a big ‘On/Off‘ switch. Brand-new ’Statistics" tab creates charts based on your blocked ads statistics, with the ability to show different types of data: total, filter-specific etc.

Also worth mentioning is the User filter. It has undergone a few changes too. The new luminous element highlighting and auto-save function, as well as a unified text field for filtering rules should make editing more convenient. The text box can also be resized to your liking.

[Added] Stealth Mode #283

We took online privacy protection in our extension to the next level by adding the Privacy module, which until this day existed only in the standalone AdGuard for Windows app. Although it doesn’t have the full capabilities of its desktop parent yet, it still makes the extension all the more effective for protecting privacy against trackers and analytical systems. It already gives you a wide range of privacy-related options (each explained in the tooltip), but we will surely add more in the future updates.

[Added] Filter categories #1068

We changed the way in which the filters are presented to users. Instead of listing them all together, we combined the filters into semantic groups. Each group includes filters that serve some particular goal. For example, filters that block ads are grouped together, filters that block trackers and serve privacy purposes will be united into a different group, etc. It is possible to enable and disable all filters in a group at once.

[Added] ‘Filters update period‘ setting #596

Before, filters were automatically updated every 48 hours (default period), now you can adjust the frequency of automatic updates (by choosing from options: every 1/6/12/24/48 hours) or disable them completely, in case you prefer to update them manually.

[Added] An option to disable integration mode while keeping the extension up #1012

If you already have the AdGuard app, our browser extension may become a very useful additional tool, which can completely replace the browser-based ’AdGuard Assistant" module (learn more). It’s called Integration mode and now you can turn it on or off in the ‘Other settings’ tab.

Common

  • [Added] An option to resize User filter and Whitelist text areas #1263
  • [Added] ‘About‘ screen #1135
  • [Added] ’Submit a complaint‘ item to the right-click menu #1072
  • [Added] $cookie modifier support #961
  • [Added] A notification with changelog after an update #1025
  • [Added] Notifications for various actions, e. g. filter updates #1167
  • [Added] Search among all filter categories #1192
  • [Added] Show notify when checking for filters update using context menu #1073
  • [Added] Update filter after enabling it #1181
  • [Changed] Information about permissions added to the extension description #1223
  • [Changed] The settings button has been hidden in the integration mode #1282
  • [Changed] A forwarder is now used for all links #1109
  • [Changed] Context menu #1150
  • [Changed] Intercept abp: subscribe links on all websites #1210
  • [Changed] Localizations have been updated
  • [Changed] Localizations have been updated #1174
  • [Changed] Update translations #1084
  • [Changed] Padding added to dropdown options #1238
  • [Changed] Wording for manual blocking tool options #1169
  • [Fixed] ‘Block WebRTC’ description inconsistency #1274
  • [Fixed] Extension uses the default value for the filters update check interval instead of the user-selected value #1295
  • [Fixed] An empty string is shown when importing a User filter #1296
  • [Fixed] Web reporter misrepresents the enabled/disabled state for filters #1293
  • [Fixed] ’Activate the most appropriate filters automatically‘ option works despite the protection is on pause #1291
  • [Fixed] Stealth Mode works despite the protection is on pause #1290
  • [Fixed] Enabled filters in disabled filter groups receive updates #1270
  • [Fixed] Mobile filter gets enabled on desktop browsers when ’Ad blocking" filter group gets enabled #1226
  • [Fixed] An empty string is created when adding the first rule via Chrome dev tools #1243
  • [Fixed] Closed tabs remain monitored in the Filtering log #1268
  • [Fixed] Self-destructing third-party cookies lead to logout from the Google account #1245
  • [Fixed] Statistics chart only works for the current day #1280
  • [Fixed] In integration mode, if the filtering disabled via assistant, extension can’t detect it #1294
  • [Fixed] ’Filters update interval’ parameter doesn’t save in settings file after exporting #1255
  • [Fixed] ’Filters update interval’ parameter duplicates after importing the settings #1254
  • [Fixed] ‘Third-party’ icon size in Filtering Log #1069
  • [Fixed] ‘Filter‘ column is empty in the Filtering log for cookie-type requests #1219
  • [Fixed] $badfilter modifier is not working with stealth exclusions #1236
  • [Fixed] $extension modifier prevents first-party URL blocking #1122
  • [Fixed] $stealth modifier issues #1225
  • [Fixed] AdGuard doesn’t hide referer properly #1217
  • [Fixed] Assistant advanced settings button doesn’t respond #1091
  • [Fixed] Custom filter is not saved when exporting settings #1224
  • [Fixed] Custom filter subscription popup doesn’t close if you move forward and backward #1206
  • [Fixed] Dropdown menu is empty when there is no statistics yet #1256
  • [Fixed] Enabled filters in disabled filter group are working #1249
  • [Fixed] Fix the issue with empty filters after update to v3.0 #1227
  • [Fixed] Import doesn’t work after deleting custom filters #1233
  • [Fixed] Import settings doesn’t import filter group settings #1232
  • [Fixed] Incorrect file types are accepted when you try to import a User filter #1039
  • [Fixed] Invalid exclusions are created using Filtering Log #1131
  • [Fixed] Self-destructing third-party cookies are not listed in the Filtering log #1262
  • [Fixed] Self-destructing third-party cookies lead to a logout from Google account #1245
  • [Fixed] Some hidden elements are not shown in the Filtering Log #1123
  • [Fixed] Some requests are not visible in the Filtering Log #1138
  • [Fixed] strip_tracking_params is applied to sub-requests #1230
  • [Fixed] The custom filter is always updated #1240
  • [Fixed] While in integration mode, new rules are not imported to the desktop AG User filter #10
  • [Fixed] Hotfix for a nasty bug with custom filters in the previous beta version: #1272
  • [Fixed] Applied element hiding rules are not visible in filtering log in some cases #1200
  • [Improvement] Users can now specify titles for their custom filters #1209
  • [Improved] ’abp: subscribe’ links are now intercepted properly #1149
  • [Improved] $csp rules are now disabled if there’s a document-level exception applied to the website #1093
  • [Improved] A validity check has been added for rules with a domain modifier #1242
  • [Improved] Extension is now more friendly towards visually impaired users #953
  • [Improved] Network requests excluded by a rule in a custom filter can now be blocked #1044
  • [Improved] Notifications for version 3.0 #1167

Chrome

  • [Improved] New permissions are made optional #1220

Firefox

  • [Fixed] Get rid of Safari and Firefox Legacy builds #1035
  • [Changed] Third-party libraries sources have been updated #1253
  • [Fixed] AdGuard extension doesn’t open the settings correctly in Firefox for Android #1264
  • [Fixed] AdGuard settings are not fully visible when accessing them from the overflow menu #970
  • [Improved] Multiple $replace rules can be applied to a single web request now #1092

Edge

  • [Changed] The default footer for MS Edge extension #1239
  • [Changed] AdGuard 2.10.8 extension for Edge blocks Spotify web player song play #1090
AdGuard Tarayıcı eklentisi
sürüm 2.10.11 2 Ekim 2018 tarihinden

Among important changes is a fix to the Assistant "block" button issue and a new "Save filtering log" feature that will come handy for filter developers and in some cases of troubleshooting via support.

  • [Added] An option to save Filtering Log when reloading the page #1074
  • [Fixed] AdGuard 2.10.8 extension for Edge blocks Spotify web player playback #1090
  • [Fixed] Assistant preview doesn't close #1083
  • [Fixed] The Norwegian translation implementation is broken #1085
  • [Fixed] When using Edge dev console, JS error occurs in extended-css.js #1086
  • [Fixed] Сosmetic filters stop working after refresh of a page cached by a ServiceWorker #1087
  • [Fixed] AdGuard "send statistics" crashes google sheets when option turned on #1096

This update adds several minor-ish (although filter enthusiasts will argue) features to the Filtering Log and improves ad blocking quality. You'll find an array of bug fixes, as usual.

[Added] Element hiding rules highlighting #1053

Applied element hiding rules are now highlighted with yellow color in the Filtering Log. This will greatly help parse log entries. We don't need to prove it to you if you are actively using it :)

[Added] Wildcard character support in rules with domain modifier #571

Again, another treat for filtering rules creators. Previously you had to list domains old-fashioned way: example.com,example.eu etc, and now you can simply use example.* syntax.

[Improved] Scripts are injected faster #1029

To efficiently block ads on the page we need a way to reliably inject our scripts before the in-page scripts are executed. A set of measures has been taken to ensure this. While there is still no 100% guarantee, the success chance has increased considerably — along with ad blocking quality.

Common

  • [Added] "Public suffix list" automatic update #1010
  • [Added] Display applied element hiding and CSS rules in Filtering log #830
  • [Added] "Filter" column to the Filtering log #863
  • [Added] Pre-processor directives for filters #917
  • [Fixed] Error in event handler for `webRequest.onBeforeRequest` #1015
  • [Fixed] Unnecessary "Cannot create rule from filter" error entries in the browser console while in integration mode #1016
  • [Fixed] Whitelist is not applied for requests sent from within a service worker #1032
  • [Fixed] Wrong filters sort order #1028
  • [Fixed] Text box is not editable in the "Block element" window #331
  • [Fixed] Incorrect layout for filter name #1050
  • [Fixed] High CPU usage because of searching hidden elements #1067
  • [Fixed] Underscore character is not displayed on Linux #393
  • [Fixed] Some Extended CSS rules are not working because of regex issues in content attribute #1079
  • [Fixed] Rules containing content substring are not working correctly while Filtering log window is open #1080
  • [Improved] Browser extension build process has been optimized #991
  • [Improved] Filters-downloader module has been upgraded to v1.0.5 #1051

Chrome

  • [Fixed] ext-CSS does not always get applied #1009
  • Firefox

    • [Fixed] Some sites are broken by `$$` rules in Firefox Quantum #1001
    • [Fixed] Element hiding rules don't work in frames by playbuzz #1046
    • [Fixed] JS rules don't work on xda-developers.com #1004
    • [Fixed] Ineffective browser.storage issue #1006
    • [Fixed] `$replace` rule does not get applied #1038
    • [Fixed] FF for Android: If you click on "AdGuard settings" nothing happens #1034

    Edge

    • [Fixed] WebSocket requests are not visible #1014

    Opera

    • [Fixed] "Activate the most appropriate filters automatically" doesn't work #997
    AdGuard Tarayıcı eklentisi
    sürüm 2.9.2 11 Nisan 2018 tarihinden

    Ho Ho Ho! Just kidding, it is not Christmas, but it might have very well been — isn’t every AdGuard Browser Extension release a special day for you? For us, it certainly is 🙂 This time we prepared a couple or two of quite important changes and improvements, to come along with a long list of more routine-ish fixes. Read on to find out the details.

    [Added] Integration with the new Assistant #956

    For a while now we develop AdGuard Assistant more or less independently, to later use it wherever we need — Windows and Mac apps use regular Assistant, Android and iOS apps use mobile version. Browser extension users encounter Assistant when they click "Block ads on this website" button. We will not go into the details here, those who interested can find the exhaustive changelog inside the Assistant repo.

    [Improved] `InsertCSS` to use instead of the content scripts #847

    There was a certain change in Chrome browser recently, that prompted us to respond by reconsidering the way we inject scripts and styles. The good thing is, thanks to this change we now have less bugs, more possibilities and were even able to make the extension more lightweight by reducing the amount of code.

    [Improved] ExtendedCss has been updated to v1.10 #980

    This change is on the technical side, but from the end user perspective it converts into better performance and better quality ad blocking, thanks to more tools being available to the extension now.

    Firefox

    • [Fixed] HTML filtering rule does not work on example.org #948
    • [Fixed] The issues with content filtering rules in Firefox #959

    Safari

    • [Fixed] Assistant crashes in Safari #974
    • [Fixed] Wrong URL blocking rule behavior on iOS #957
    • [Fixed] Styles are applied twice in the Safari extension #979
    • [Fixed] Safari content blocker converter fails if we pass it an invalid rule #945
    • [Improved] SafariContentBlockerConverter memory usage #955

    Edge

    • [Fixed] Wrong filter names language #889

    Common

    • [Fixed] Some regex rules don't work #978
    • [Fixed] Can't build the extension with Maven 3.5.2 #946
    • [Fixed] Assistant menu doesn't save its position on pages #973
    • [Fixed] Assistant does't block in 'Preview' mode #975
    • [Fixed] Element hiding exclusion can't be applied to iframe #934
    • [Fixed] Filters are not getting updated after the clean install #981
    • [Fixed] Assistant dialog default position is different from where it should be #976
    • [Fixed] AdGuard extension for Yandex Browser prevents downloading of .pdf files on vk.com #897
    • [Fixed] Rules proposed by AdGuard for "content-security-policy-check" are incorrect #941
    • [Fixed] Warning Page Appears Twice #995
    • [Fixed] Extension can't detect it when you disable filtering in Adguard for Win via Assistant #989
    • [Improved] Old links have been replaced with new ones #952
    AdGuard Tarayıcı eklentisi
    sürüm 2.8.4 2 Şubat 2018 tarihinden

    Ad blocking has been enhanced in this version by adding support for several modifiers. We've also integrated the extension with our web reporting tool, details below. As usual, all spotted bugs have been fixed too, this mostly concerns Firefox version.

    Common

    [Added] Integration with reports.adguard.com #894

    A new convenient way to report any issues with websites, be it missed ads, false positives, unblocked social widgets etc. Just head to the problematic website, bring up the context menu and select "Submit a complaint" option. You will be transferred to reports.adguard.com and a wizard will take you through the required steps to report the issue — and most of the fields will be even filled out automatically. Try it!

    • [Added] $badfilter modifier support #866
    • [Fixed] onet.pl shows anti adblock notice #860
    • [Fixed] Errors in the browser console #865
    • [Fixed] Blog link in the footer #908
    • [Fixed] Double scroll bar in filtering log #907
    • [Improved] AdGuard now filters "New tab" windows #881
    • [Improved] Styles protection has been enhanced #829
    • [Improved] "ExtendedCss" module has been upgraded to v1.0.9 #906

    Chrome

  • [Fixed] Browsing security fails in Chrome incognito mode #905
  • Safari

  • [Added] $important modifier support #877
  • Firefox

    • [Added] $replace and $$ rules partial support #864
    • [Fixed] Huge amount of writes by storage.js.temp #892
    • [Fixed] Search option misbehaves on news.yandex.ru #872
    • [Fixed] Recaptcha is hidden by AdGuard on vk.com #880
    • [Fixed] Content filtering rules aren't visible in the filtering log #910
    • [Fixed] group.aliexpress.com #924
    • [Fixed] "Thank you" page switches don't change the extension settings #929
    • [Fixed] AdGuard for Firefox hides iframe with text area on insanelymac.com #922
    • [Fixed] Beta 2.8.2 Doesn't save whitelist settings after reboot (Beta 2.8.1 works) #933
    AdGuard Tarayıcı eklentisi
    sürüm 2.6.5 22 Ağustos 2017 tarihinden

    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.

  • [Improved] Global variables were got rid of: #451
  • [Improved] Tabs API: #374
  • 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.

  • [Changed] The build process for v2.6: #600
  • [Changed] The build process was changed so that all Adguard's code is encapsulated into a reusable API: #454
  • 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