تاریخچه نسخه ها | AdGuard

Our filter team sharpened their blades again. Ads stand no chance, and stability is up too.

The extension now runs more smoothly thanks to this minor update, which fixes a number of bugs.

Changelog

Fixes

Move clipboardRead and clipboardWrite permissions to optional AND request them on User Rules Entry and Allowlist (mobile version) #3364

The extension doesn't work in browser 360 #3058

Changelog

A small fix that addresses the issue with the Update Notification appearing intermittently #3385

Patch 3 for AdGuard Browser Extension v5.2 brings several improvements to the app’s usability and appearance.

The most significant change is that now you can update your custom filters seamlessly with just one click. This became challenging after moving to MV3, but the function is back.

Also, we have added an animated loading icon for the extension popup, so now you can easily check if the extension is up and running.

Changelog

Improvements

Added the possibility to update custom filters in the MV3 version of the extension #3016

Added a new animated loading icon for the extension popup

This release removes previously unnecessary permissions and updates how the extension handles permission requests.

The extension now runs more smoothly thanks to this minor update, which fixes a number of bugs.

Changelog

Fixes

Minimize the extension update fetch response size in MV3.

The extension is failed to update via the popup #3317.

AdGuard Browser Extension v5.2 is here with a ton of updates that significantly enhance usability. You’ll find the full changelog below, but here are the standout features we’re most excited about.

Custom filters

You can now add your own custom filters in the MV3 extension! This feature had to take a break after our migration to MV3 because of API limitations, but it’s finally back and ready for you to use.

If there are rules that aren’t included by default but you’d like to use, simply add them right in the extension. This is powered by Chrome’s new User Scripts API, which means custom filters work a bit differently under the hood.

The User Scripts API is a set of browser-provided functions and capabilities that allow extensions to run custom JavaScript scripts on web pages. These are often used to modify or enhance websites in ways that aren’t originally provided by the website itself.

To add your own rules:

Go to Settings → Filters. Under the Custom section, you’ll see a warning prompting you to enable Allow User Scripts. Click the link to open your browser’s extension settings.

Toggle the Allow User Scripts option to enable it.

Return to the Filters tab, open Custom, enable it using the switch in the upper-right corner. Click Add custom filter.

With the User Scripts API, now you can also apply scripts in user rules that aren’t included in the built-in extension filters. To do this:

Go to Settings → User rules. You’ll see a warning prompting you to enable Allow User Scripts. Click the link to open your browser’s extension settings. Toggle the Allow User Scripts option to enable it. Return to the User rules tab. Click Import or write your own rule and click Save.

Update checks

In MV3, filters are now updated together with the extension itself. Until now, new filters could take a long time to reach you, because every update had to go through Chrome Web Store reviews. Recently, Chrome introduced a skip review option that significantly speeds things up.

We’ve improved our build process so that our updates are now more likely to go through this fast track, meaning you’ll get the latest filters much sooner. We also added a Check for updates button — if you don’t want to wait, you can now trigger an update check yourself with a single click.

Blocking page

We’ve redesigned the blocking pages in the MV2 extension and added them to the MV3 one. Now, when a blocking rule with the $document modifier is triggered, you’ll see a clearer, more informative warning page. Also, if you’re about to visit a potentially dangerous website, the MV2 extension now greets you with a redesigned safe browsing warning that is easier to understand and act on.

Design improvements

And finally — good news for everyone! We’ve enhanced accessibility for visually impaired users, making sure AdGuard is inclusive and easy to use for more people.

Changelog

Improvements

Added ability to update the extension with filters manually in MV3

Decreased time period for temporary exceptions caused by clicking Proceed anyway on a blocking page from 40 minutes to 10 seconds #3263

Removed overflowing notification text in the options page

Blocking page for requests blocked by $document rules in MV3

Added support for Chrome’s User Scripts API that allows more reliable script injection in MV3

Send last filter update time during issue reporting #3055

Added ability to exit editor by pressing the Escape keyboard button #2333.

Added сompatibility of $header modifier with $match-case and $third-party modifiers in MV2 #2942

Added zip and crx artifacts for the extension builds #3163, #2488

Restored support for custom filters thanks to the User Scripts API

Updated blocking pages in MV2 extension for Browsing Security and for web pages blocked by $document rules

Improved accessibility for visually impaired users #3035, #2315, #2332

Removed AdGuard DNS filter and AdGuard Annoyances filter as deprecated

Increased file size limit to 10MB for $replace rules in Firefox #3192

Updated @adguard/dnr-rulesets to v3.2.0

Updated @adguard/filters-downloader to v2.4.2

Updated @adguard/assistant to v4.3.75

AGTree (A tool for working with adblock filter lists)

Updated @adguard/agtree to v3.2.3

AdGuard Logger (A tool for logging from AdGuard extensions)

Updated @adguard/logger to v2.0.0

Fixes

Cursor moves to the end when saving user rules #3145

Cannot maximize Filtering log in Firefox for Windows #2464

Unable to paste text into user rules input field on Android #3061

Invalid HTML rule selectors are breaking website loading #2646, #2826

Stealth mode’s Hide Referer from third parties option may break some websites #2839

Filtering log: Resizing the right panel selects its contents #2305

Types of the blocked requests are not displayed in the popup (Firefox for Android) #3157

Switching to the Statistics tab shifts the Actions and Statistics buttons (Edge for Android) #3158

Filtering log: Request details panel is automatically closed when loading a website in another window/tab #2327

Scriptlet rules are not displayed in the filtering log #3164

The filtering in Edge’s split screen doesn’t work #2832

Total blocked popup string translated incorrectly #3204

$replace rules may break some websites #3122

Missing space in the description of AdGuard German filter in the de locale #3216

OOM (Out of Memory) errors may occur when applying too many patches in a row in MV2 #3230

File size limit too low for $replace rules in Firefox #3192

Attributes without value are not allowed for HTML filtering rules #147

Firefox extension doesn’t launch on browser startup #3189

Wrong rule is displayed for pages blocked by $document rule in MV3 #3260

Overflowing notification text in the options page

Minor fixes.

Fixed an issue causing a memory leak.

Changelog

Fixes

MV2 extension crashes in MS Edge #3230

This is a quiet and unassuming patch: it brings small tweaks that make things work better. Sounds simple, and sometimes simple is just what one needs.

Changelog

Improvements

AGTree (A tool for working with adblock filter lists)

AGTree updated to v3.2.0

TSUrlFilter (AdGuard Browser Extension filtering engine)

TSUrlFilter updated to v3.3.3

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

TSWebExtension updated to v3.1.0-alpha.3

Small but important hotfix.

Changed

Updated @adguard/agtree to v3.1.3.

Updated @adguard/dnr-rulesets to v3.0.0-alpha.3.

Updated @adguard/tsurlfilter to v3.3.1.

Updated @adguard/tswebextension to v3.1.0-alpha.1.

Minor fixes.

The extension now runs more smoothly thanks to this minor update, which fixes a number of bugs.

Small but important hotfix.

The extension now runs more smoothly thanks to this minor update, which fixes a number of bugs.

With this release, we're bringing our MV2 and MV3 extensions on the same page. We’re upgrading the MV2 extension to version 5.1, and from this point on, both extensions will be in perfect sync, with their versions updated at the same time.

What’s in it for you? First off, you’ll notice a visual upgrade: the MV2 extension now features the MV3 design. But that’s not all — from now on, bug fixes and features will be implemented more efficiently in both extensions.

We’ve also made some other minor improvements and bug fixes, which you can explore in the full changelog below. One of them deserves to be highlighted: internal optimizations will give the extension the possibility to take part in the Fast Track Review process in the Chrome Web Store. This means that in the future, if our approach works, we will be able to release extension updates with new filters more often, without having to wait for a review according to Chrome Policy. You will get extension updates in your hands – or rather, in your browser – faster than ever!

Changelog

Improvements

Expanded dynamic rules quota by implementing Safe and Unsafe rules

Optimized performance of parsing uBlock filter parameters #2962

Added support for log error when regex is not supported #3004

Improved the way the extension counts statistics

Added the ability to search by domain in the field “Search in tabs” in the Filtering log #3028

DNR rulesets are now displayed in the About tab #3054

Improved memory consumption #3037

Modified byte ranges for faster extension updates

Fixes

runtime.connect error due to the back/forward cache

Content scripts are injected between extension wakeups

Declarative rule logging in the Filtering log

Allowlisted stealth rules are not shown in the Filtering log #2950

Adding custom filters from Google Drive #2908

Allowlist tab considers all websites in the tab as allowlisted #3020

The counter is blocked on the popup updates for blocked requests from other tabs #3050

A rule from a disabled filter list disables another rule #3002

$popup, third-party modifiers cause document blocking #3012

User rules editor hangs in Chrome and errors in Firefox when adding regex rule

Lines for absent metadata are removed when adding a custom filter #3057

react-router causes a feature flag warning in options page

Shortened extension name to fix the layout on Firefox for Android #3075

Cosmetic rules are applied to the Assistant frame

Filtering log doesn't detect opening of new tabs

Pattern shortcut extraction from regexp patterns with character classes #2924

$removeparam incorrectly removes parameters from encoded URLs

Scriptlets and scripts are executed too late on website reload or navigation in MV2 #2855

AGTree (A tool for working with adblock filter lists)

AGTree updated to v3.0.0-alpha.5

Scriptlets (JavaScript enhancement for filtering rules)

Scriptlets updated to v2.1.4

TSUrlFilter (AdGuard Browser Extension filtering engine)

TSUrlFilter updated to v3.1.0-alpha.8

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

TSWebExtension updated to v3.0.0-alpha.1

Unfortunately, the build with the returned Quick fixes filter failed to pass the Chrome Web Store review and we had to remove not only this filter, but also the entire Custom filters group. We're very unhappy about this, but it's a forced measure.

Stay tuned to our blog for our reflections on this matter and a full timeline of events, as well as how the userScripts API and fast-track review can potentially help us.

Changelog

Removed

Removed AdGuard Quick Fixes filter.

Removed Custom filters group.

Small but important hotfix.

Changelog

Changed

Scriptlet rules are available only from the pre-built filters now. Now, of the script and scriptlet rules that are added to Custom filters, User rules or Quick fixes filter, only those already used in pre-built filters will work. This means that before applying such a rule, the extension engine will compare the rule body with the list of rules that have already been used in filters from all categories of pre-built filters, such as Ad Blocking, Privacy, etc. If there is a match, the engine will apply the rule, and if not, it will discard it. For example, let's imagine that the Base filter contains the rule example.com#%#console.log('test'), then the engine will accept rules like example.org#%#console.log('test') and #%#console.log('test'), but will discard example.com#%#console.log('new test').

Added AdGuard Quick Fixes filter.

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

TSWebExtension to v2.4.0-alpha.10.

Removed

Injection of remotely hosted scripts.

How to install MV3 stable:

Chrome

How to install MV3 beta:

Chrome

The bad news is that we had to remove the Quick Fixes filter due to the problems with passing the store review — MV3 restrictions in action. The good news is that we updated other filters — which means that ads will be blocked better.

Small but important hotfix.

Changelog

Changed

Remade JS rules injections in MV3:

use chrome.scripting API for injecting functions for script rules from the pre-built filters.

use script tag injection only for script rules manually added by users — rules from User rules and Custom filters.

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

TSWebExtension updated to v2.4.0-alpha.8

Removed

Ability to execute new AG_ script rules from User rules and Custom filters in MV3.

How to install MV3 stable:

Chrome

How to install MV3 beta:

Chrome

The extension now runs more smoothly thanks to this minor update, which fixes a number of bugs.

For those who have noticed memory leaks, this release will help. But even if you haven’t spotted any problems, it's still worth it to update — new versions always bring better filtering quality.

Changelog

Improvements

Send manifest_version during issues reporting

Optimized performance of parsing uBlock filter parameters #2962

Fixes

$removeparam fails to match encoded URL params #3015

Memory leak caused by multiple script injections on the same pages after an event page in Firefox restarts in MV2 #2594

AGTree (A tool for working with adblock filter lists)

AGTree updated to v2.1.3

TSUrlFilter (AdGuard Browser Extension filtering engine)

TSUrlFilter updated to v3.0.7

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

TSWebExtension updated to v2.0.7

The extension now runs more smoothly thanks to this minor update, which fixes a number of bugs.

Fixed a memory leak issue that occurred due to multiple script injections on the same pages after restarting a service worker or event page.

Changelog

Fixes

Memory leak #2594

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

TSWebExtension updated to v2.4.0-alpha.7

A small but important hotfix.

Changelog

Fixes

Filter groups do not turn back on after being turned off #3026

Think about this patch as a breath of fresh air: bugs have been fixed and features have been polished. No more problems while trying to open user rules in a new window. Now you can enjoy a better user experience.

Guess what we’ve got hidden under the hood? Nope, it’s not a spooky mask for Halloween — it’s a few changes to the extension that are all about the treats, not the tricks.

October 14–18 – what a week in history! In 1929, Walt Disney decided to bring a little magic into the world by founding his studio. Meanwhile, in 1793, Marie Antoinette learned the hard way that “Let them eat cake” doesn’t work out so well at a guillotine party. Also this week, a few bugs have been fixed in your browser extension. Small fixes, sure, but without them, who knows what kind of digital chaos we’d be facing? History could’ve taken a wild turn…

Changelog

Fixed

Excluding request types causes document blocking #2992.

Selecting a single $permissions filtering log event selects all $permissions events

AdGuard Logger (A tool for logging from AdGuard extensions)

Logger updated to v1.1.1

TSUrlFilter (AdGuard Browser Extension filtering engine)

TSUrlFilter updated to v3.1.0-alpha.7

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

TSWebExtension updated to v2.4.0-alpha.4

The extension now runs more smoothly thanks to this minor update, which fixes a number of bugs.

Changelog

Fixes

Invalid rules break the UI of the popup #2989

Selecting a single $permissions filtering log event selects all $permissions events

AdGuard Logger (A tool for logging from AdGuard extensions)

Logger updated v1.1.1

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

TSWebExtension updated to v2.0.4

Life’s got its fair share of mysteries: Why are we here? No clue. What’s the meaning of existence? Still a puzzle. How many updates will it take to bring the browser extension to perfection? Hard to say exactly, but with this release we’re one step closer to finding out the answer to this one — here’s a few bug fixes for a more solid ad blocking.

Changelog

Fixes

MV3-specific filters are not used in Edge if the MV3 extension is installed #2985

Cosmetic rules sometimes are not applied or are applied to a wrong domain #2984

JS rules are blocked by Trusted Types on some websites #2980

MV3 extension cannot apply rules to about:blank iframes #2975

Scriptlets logging does not work #2977

Content-type matching of $permissions and $removeparam rules #2954

AdGuard Logger (A tool for logging from AdGuard extensions)

Logger updated to v1.1.0

TSUrlFilter (AdGuard Browser Extension filtering engine)

TSUrlFilter updated to v3.1.0-alpha.6

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

TSWebExtension updated to v2.4.0-alpha.3

This time, we’re focusing on design enhancements. We’ve improved the styles for the extension popup, notifications, and the User rules section. Plus, we’ve sprinkled in some UI magic by refining a few settings descriptions and adding a warning about unsaved changes in the Allowlist and User rules editors.

Oh, and the “Polish GDPR-Cookies Filters” filter, available in the MV2 extension, is now also available in the MV3 extension.

Changelog

Scriptlets (JavaScript enhancement for filtering rules)

Scriptlets updated to v1.12.1

TSUrlFilter (AdGuard Browser Extension filtering engine)

TSUrlFilter updated to v3.1.0-alpha.5

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

TSWebExtension updated to v2.3.0-alpha.1

Fixed a nasty bug: filtering on some websites didn’t work due to the Hide your search queries feature. Now it works.

Changelog

Fixes

Hide your search queries breaks some websites #2969

Not so long ago, we successfully migrated our extension to Chrome’s new API, and now, when you download AdGuard Browser Extension from the web store, you’ll automatically get the new MV3 version. But what if you want to stick with the MV2 extension? No worries, we’ve got you covered, at least for now – it will keep working as long as Google continues to support the old API. As for where to find it: we’ve moved the MV2 extension to the spot where the beta used to be available.

Changelog

Fixed

The exception $domain=~ filtering rule is not working properly #2912.

Scriptlets exclusion matching is not working properly for rules with arguments #2947.

Scriptlets (JavaScript enhancement for filtering rules)

Scriptlets updated to v1.12.1.

TSUrlFilter (AdGuard Browser Extension filtering engine)

TSUrlFilter updated to v3.0.5.

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

TSWebExtension updated to v2.0.3

AGTree (A tool for working with adblock filter lists)

AGTree updated to to v2.1.2

AdGuard Logger (A tool for logging from AdGuard extensions)

Logger updated to v1.0.2

It hasn't been long since the migration of our browser extension to MV3 was completed, but we're already back with a small beta that brings some design improvements. It's really just a special touch: fixes in the UI for a better user experience.

After the update, some users experienced incorrect operation of the extension — ads were not blocked at all. This could have happened due to rule conversion errors, but thanks to this hotfix, everything is back to normal. Now you can customize ad blocking to your liking and see no ads.

Changelog

Fixes

The extension stopped working because of intersection of dynamic rules IDs #2953

The list of custom filters is passed to ReportsWebApp even if the Custom group is disabled #2951

The time has come for a big move: the release is out and our trusty ad-blocking extension is now fully compatible with MV3. Let’s take a look at what’s changed.

If you’re already using our extension for Chrome, your existing extension will be replaced with the MV3 one. New users can install it from the Chrome Web Store

Features and functionality

Statistics. The statistics screen is similar to the query log in AdGuard DNS and provides a categorized view of URLs by company, sorted by type. All data is processed on your device, ensuring complete privacy. We only show which requests were sent to which category: Advertising, Trackers, Social media, CDN, and Other.

Two versions of the filtering log. There is the regular version with “assumed rules” since the browser doesn’t provide specific details about which declarative rules were applied. So in the regular Filtering log, you’ll only see the approximate rules that were applied.

The other version contains more precise information, but to see it you’ll need to install the “unpacked” version of the extension into your browser to access it.

Network rules and limitations. With MV3, network rules are now mostly applied by the browser, which introduces some limitations. However, cosmetic rules are still managed by our engine and function well. More details about the limitations can be found on GitHub.

Quick fixes. AdGuard Ad Blocker MV3 introduces the AdGuard Quick Fixes filter. Why do you need it?

With Manifest V3, we can’t update filter rules dynamically because the rules are now built into the extension and are only updated with the extension itself. This is not very convenient.

We found a way around this: the new filter uses dynamic rules and provides the most reliable operation of our filters. AdGuard Quick Fixes uses dynamic rules to make adjustments in real time without significantly affecting the user’s dynamic rules limit. It’s fast, efficient, and perfect for seamless filtering in the demanding MV3 environment.

Help wanted. The Help develop AdGuard filters option is back in the release version. You can anonymously share your filter usage data to help us improve ad blocking capabilities for everyone.

A fresh look: UI enhancements

This release brings a cleaner, more user-friendly interface. These are just a few examples:

The loader has been improved in several scenarios, such as switching between pause modes, adding websites to the Allowlist, changing user rules, and switching filter groups.

New loading states for enabling, disabling, and pausing protection.

A splash screen with the AdGuard logo now appears during loading.

The Enable button for the annoyance filters consent is now more accessible and is displayed without scrolling.

Bug fixes and improvements

No journey to a full release is without its bumps. Here’s just a part of what we’ve smoothed out:

Fixed incorrect conversion of regular expressions rules

Resolved issues with the $popup and $badfilter modifiers

Cosmetic rules are now applied faster

TSUrlfilter and Scriptlets are minty fresh

If you find any bugs or have any suggestions, don’t hesitate to contact us on GitHub

Chrome users can install AdGuard Ad Blocker MV3 from the Chrome Web Store.

If your extension has been updated to v4.4, you may have noticed some websites haven’t been working properly lately. That’s on us: the $redirect modifier wasn’t handling ads correctly, causing occasional lags and forcing some users to refresh the page they were visiting to get things working again. This hotfix solves that problem and brings other improvements.

Changelog

Fixes

The ‘$redirect’ rule causes a CSP (Content Security Policy) error instead of redirecting #2913

Negated domains with the $to modifier are not working as expected #2910

TSUrlFilter (AdGuard Browser Extension filtering engine)

TSUrlFilter updated to v3.0.1

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

TSWebExtension updated to v2.0.1

Scriptlets (JavaScript enhancement for filtering rules)

Scriptlets updated to v1.11.16

It’s time to introduce the latest AdGuard Browser Extension v4.4.18! While you might not spot any visible changes, rest assured, we've been working hard behind the scenes. This update focuses on enhancing how rules and filters are managed, all thanks to the integration of AGTree to the TSUrlFilter library.

AGTree is a powerful tool that streamlines how ad-blocking filter lists are handled. It’s now part of the TSUrlFilter library that we’ve integrated into various products, including browser extensions. By implementing AGTree across different platforms, we’re aiming for a more unified approach, which allows us to use a single library for tasks such as conversion, parsing, and validation of blocking rules. The result? Improved content blocking, faster filtering engine startup, and simplified rule analysis and conversion.

And how does this benefit you directly? Moving to AGTree enhances your security by minimizing the risk of filtering errors. This means a more accurate ad and tracker blocking experience as you browse. Additionally, along with the AGTree transition, this release includes significant updates to Scriptlets that ultimately boost the overall performance of the extension.

Changelog

Improvements

More convenient name format for exported settings file #2607

Fixes

$cookie exclusion breaks websites in Firefox #2552

prevent-xhr scriptlet is having problems #2063

$redirect modifier does not fake Response.prototype.url #2278

Filtering log gets refreshed when navigating Yandex Maps #2519

Filtering log is broken by history.replaceState #2598

$generichide modifier prevents URL blocking rules from working correctly #2690

Blocked ads count leaks between websites when opened in the same tab #2080

Broken document loading on download.ros.org #2194

Automatic filters update does not work in mobile browsers #2423

Opening URLs starting with "view-source" in Firefox gives errors #2549

Filter groups can’t be opened, if some text is selected on the page #2662

Errors in the console when using the 'Self-destruction of first-party cookies' option #2683

lastCheckTime isn’t updated on auto-update #2726

Some websites using strict CSP rules can block AdGuard scripts in Firefox #1733

Style filter is applied, but scriptlet filter is not in Firefox #2782

AdGuard menu doesn’t open in Firefox Nightly #2817

Information about enabled custom filters is not passed to the reports tool #2793

Some filters are not updated when enabled #2818

Scriptlets (JavaScript enhancement for filtering rules)

Scriptlets updated to v1.11.6

TSWebExtension (AdGuard Browser Extension filtering engine)

TSWebExtension updated to v2.0.0

TSUrlFilter (AdGuard Browser Extension filtering engine)

TSUrlFilter updated to v3.0.0

Sometimes the problem is not us. And this is one of those times: the AdGuard menu didn’t open in the Firefox browser, and it fell on us to find a solution while waiting for a bugfix from Mozilla. Well, this hotfix is the solution.

Changelog

Fixes

AdGuard menu doesn’t open in Firefox Nightly #2817

New release, new challenges. In this beta we've worked on the reliability of the AdGuard scripts in the Firefox browser: now they can withstand even the strictest CSP rules on a site, which means more ads will be blocked. And one more change: some errors related to the Self-destruction of first-party cookies option will no longer be displayed in the console.

Changelog

Fixes

Errors in the console when using the Self-destruction of first-party cookies option #2683

Sites with strict CSP may block AdGuard scripts in Firefox #1733

TSWebExtension (AdGuard Browser Extension filtering engine)

TSWebExtension updated to v1.0.24

No one expected another patch for the AdGuard Browser Extension but here it is. Hopefully it’ll make your ad blocking experience a little smoother. We fixed a major issue where some users couldn’t install the extension properly because they couldn’t access the file with available filter lists on our server. And after some hard work (and maybe a little sweat), the $all and $popup modifiers should now work as our developers intended.

Changelog

Improvements

Check filter checksum after it is downloaded #2681

Fixes

The extension install process stops if filters.js is unreachable #2761

The $all modifier does not work in the currently opened tab #2620

Broken patch updates occur when activating a group of filters #2714

If some fatal error occurred during the last update, diff updates were fetched before full sync #2717

Assistant iframe styles are affected by cosmetic rules specific for websites #1848

$popup disables simple blocking rule #2728

$all modifier does not block loaded resources of the page #2753

Scriptlets (JavaScript enhancement for filtering rules)

Scriptlets updated to v1.10.25

A small update that paves the way for bigger ones. Fixed the link in the extension’s beta update notification and the bug where filters would roll back to pre-installed ones when importing settings.

Changelog

Fixes

Link in the extension’s beta update notification leads to wrong release notes [#2682] (https://github.com/AdguardTeam/AdguardBrowserExtension/issues/2682)

The filters roll back to the pre-installed ones when importing settings [#2735] (https://github.com/AdguardTeam/AdguardBrowserExtension/issues/2735)

As any ad blocking enjoyer will tell you: a good ad-blocking extension shouldn’t gobble up too much memory, leaving your computer gasping for air with each new tab. As proud ad blocking enjoyers, we squash bugs that cause memory leaks like nobody’s business. And while we’re at it, we’ve also fixed a few other bugs and updated Scriptlets.

Changelog

Fixes

A bug causing a memory leak

Settings failed to open on the very first attempt #2712

After installation, all groups and filters are disabled #2713

Custom filter subscription UI looks incorrectly on Android #2715 #2697

Block trackers is not sent as a parameter via the Report tool #2721

Scriptlets (JavaScript enhancement for filtering rules)

Scriptlets updated to v1.10.1

Review status:

Chrome: Published (Phased release at 100%)

AMO: Published

Opera: Published

Edge: Published

May the force of the extension be with you! Our Jedi developers have been working tirelessly in order to bring ~~peace to the galaxy~~ you an improved version of AdGuard Browser Extension.

What is the core of any ad blocker? The correct answer is “filter lists”. Once AdGuard is enabled, rules in filter lists are responsible for making web pages look nice and clean. It’s essential to keep the filter lists up-to-date. But every time there is even a small change in a filter list, a problem occurs: the ad blocker needs to re-download the whole list. That sounds pretty inefficient.

In this version we have added differential update capabilities. Now instead of fetching the entire filter list, the extension will only download the changes that were made in a list since the last update. This also helps us to achieve a more efficient and user-friendly experience by reducing bandwidth consumption, minimizing latency, and decreasing server load. To put it simply, now AdGuard can download filter lists updates much more frequently, so you will enjoy the most efficient ad blocking.

We have also fixed the problem that occurred when users tried to access websites with enabled Stealth Mode options in the extension settings. Rules did not work correctly, so some websites wouldn't open. We have fixed this issue, so now the rules will disable Stealth Mode when it’s necessary.

We have also fixed some minor issues as well as improved the performance and stability. We hope you’ll enjoy the new version of AdGuard Browser Extension 4.3.

Changelog

Improvements

Added differential updates capabilities #192

Fixes

iCloud mail doesn’t open with enabled Stealth mode #2660

AdGuard Browser Extension doesn’t work in Firefox 91 (ESR) #2661

AdGuard Browser Extension doesn’t work in 360 Browser 13.0 #2626

Unable to unblock referrer by custom rules #2648

Cosmetic rules with wildcard don’t work on some domains #2650

Automatic filters update does not work in mobile browsers #2423

Not all custom filters are shown in the list #2693

Scriptlets (JavaScript enhancement for filtering rules)

Updated Scriptlets to v1.9.105

Unwrap the festive fun with our latest release. So, what are you waiting for? Get your AdGuard Browser Extension updated and let the jingle bells (and ad-free browsing) ring!

We’ve released another update to fix the bugs that we found in the previous version. One of the main problems was with the Firefox browser. Firefox users with the older version of the browser couldn’t use AdGuard Browser Extension. We’ve solved this issue in the new version.

Additionally, we’ve made some minor tweaks to improve the overall performance of AdGuard Browser Extension, updated Scriptlets and the About page.

Changelog

Improvements

Remove referrer from the document.referrer#1844

Show versions of used libs on the About page #2237

Fixes

'this [#api] is undefined' error #2636

If Filtering log is closed, browser console scriptlet logging is disabled #2584

Modified cookies requests aren't displayed in modified log events #2512

TSUrlFilter library is loaded in the rules editor #2412

Font is inconsistent in the "Filters updated" popup notification #2309

$$ rules break encoding on some websites #2249

Scriptlets (JavaScript enhancement for filtering rules)

Scriptlets updated to v1.9.101

We're releasing this hotfix to solve one very important issue with cosmetic rules logging.

This is another update aimed to fix bugs left over from the v4.2 release. We've solved some of the memory leak issues with tabs open for a long time, reduced the time to apply rules on a webpage, not to mention other minor and less significant tweaks. Also, the AdGuard Browser Extension is now available in Macedonian — thanks to our contributors!

Changelog

Improvements

Added Macedonian localization #2574

Fixes

remove-node-text scriptlet does not work on the first visit to the website #2505

Filtering log collects logs even when closed #2544

Ads are not removed on the first visit to 'pikabu.ru' #2571

Cannot add a custom filter list with a .php URL #1723

The AdGuard settings… option is located in the context menu on the extension's settings page and leads to itself #2258

zh-CN localized metadata is used for zh-TW UI language #2504

The Report an issue form incorrectly identifies the browser #2250

The filtering log crashes when trying to create a blocking rule for the removeparam exclusion #2534

Cannot open filtering log in the Firefox Mobile browser #2536

The extension logo is displayed incorrectly #2536

Scriptlets (JavaScript enhancement for filtering rules)

Scriptlets updated to v1.9.91

TSWebExtension (AdGuard Browser Extension filtering engine)

TSWebExtension updated to v0.4.6

The extension now runs more smoothly thanks to this minor update, which fixes a number of bugs.

Hopefully, this update will bring something nice into your everyday browsing — at least if you’re a YouTube or Android user.

Addressing YouTube’s ad blocker detection

Some users reported that AdGuard was detected on the YouTube website — they could not watch videos without disabling the extension. To address this issue, we’ve updated our scriptlets.

Adapting for Firefox on Android

Firefox for Android is making changes, and we’re keeping up. To continue working with Android, the extension for Firefox now uses event pages. But this change is rather unnoticeable.

Changelog

Improvements

Remove unclickable space between menu items #2198

Automatically fill out OS name and version when reporting incorrect blocking #2535

Fixes

Labels of radio buttons and checkboxes are not clickable in the rule wizard #2204

Scriptlets (JavaScript enhancement for filtering rules)

Scriptlets updated to v1.9.83

Important for filter maintainers

Add !#else pre-processor directive support #20

We continue to clean up the bugs left over from the v4.2 release. This patch addresses a number of issues mainly concerning filtering, which should now work smoothly.

Changelog

Fixes

The Proceed anyway button is not working for domain names above the second-level domains #2497

Scripts using <AGPolicy> do not work correctly on websites with Trusted Types #2068

AdGuard Browser Extension doesn't inject scripts into frame in Firefox on welt.de #2190

Unable to apply rules to some <iframe> HTML elements #2328](https://github.com/AdguardTeam/AdguardBrowserExtension/issues/2328)

Unable to apply CSS rules inside <iframe>#2420

In the Filtering log, the tab selector is not updated according to the tab title #2428

Russian translation in Edge when installing AdGuard Browser Extension from Microsoft Edge Add-ons #2430

Filters activation issues #2431

$removeparam modified requests are not displayed in the Filtering log #2442

Some duplicates are retained when importing user rules #2446

The Filtering log crashes when trying to create an exclusion for a CSP rule #2448

A tab loading is blocked by $popup modifier rule on direct URL navigation #2449

Filtering log does not show applied Stealth mode options #2455

Invalid unblocking rule suggested in the Filtering log #2456

The $removeparam rule triggers clearing of the Filtering log #2457

A webpage does not reload when the state of AdGuard is changed #2471

The logging of applied scriptlets fails to function when the Filtering log is open #2481

Unable to open the Filtering Log for the current tab from the extension popup if a different tab was previously selected in the Filtering Log #2482

Modified cookies requests aren’t marked as modified by Stealth mode rules #2487

$csp and $removeparam allowlist rules are not being logged

Filtering log crashes when unblocking scriptlet rule

AdGuard Browser Extension v4.2.168 is malfunctioning in Firefox for Android after an update #2501

Design

Improved the description of optimized filters #2468

This hotfix addresses several issues and fine-tunes the extension for an even smoother browsing experience.

We’ve fixed the most important bugs so, among other things, all rules will now be applied correctly from the get-go and you’ll be able to keep track of blocked requests more accurately.

Changelog

Fixes

Specific rules not applied in the new tab on the first opening #2459

The number of blocked requests in the extension menu is less than in the filtering log — redirects are not counted #2443

Domains from the allowlist are not properly escaped before being passed into the regular expression rules #2461

Custom filter name is not shown in the filtering log #2454

Versions

Scriplets updated to v1.9.72

We have identified and fixed several critical bugs that were reported after AdGuard Browser Extension v4.2 for Chrome was deployed to 5% of our user base. These bugs were affecting the functionality of the extension and causing crashes for some users.

To address these issues, we have released a hotfix. We will continue to monitor the situation closely. If no further critical bugs are reported, we will gradually increase the rollout to all users.

We apologize for any inconvenience this may have caused and appreciate your patience and understanding as we work to improve the extension.

Changelog

Fixes

Do not expose JS rules in global scope #2440

AdGuard occasionally stops blocking ads #2438

Sometimes no context is created on a new tab #2433

The new version of AdGuard Browser Extension has undergone major changes that are not immediately noticeable. We’ve rewritten the whole filtering code in TypeScript and moved it into a new, separate library — this allows us to prepare the extension for a seamless transition to MV3.

A bit of background

Some time ago, we moved the extension's URL filtering engine into a separate library called tsurlfilter. The main purpose of the library is to reuse the filtering logic in our products (browser extensions for Chrome and Firefox, rule converter for Safari, linter, etc).

The tsurlfilter had two main parts:

A filtering engine that matches URLs against the rules loaded into it

A Chrome- and Firefox-specific programming interface responsible for applying the rules found

With MV3, we need to maintain filtering code not only for different browsers, but also for different manifest versions, as well as provide a seamless transition from MV2 to MV3 as browsers remove the old API. We're in no hurry to move to MV3 right away as its API is very limited.

Adding new logic to solve this problem in tsurlfilter would have made the library too heavy, so we decided to design a new software platform that would hide the logic specific to different browsers and manifests behind a single and simple API. The new library was named tswebextension.

The new `tswebextension` library

With tswebextension, it will be easier to maintain and update our products.

In the new version of the Browser Extension for Chrome and Firefox, we’ve completely redesigned the background service using tswebextension — this will allow us to seamlessly move to MV3 in Chrome in future major releases.

In addition, we’ve updated the AdGuard API that also uses tswebextension under the hood.

Changelog

Features

Clicking any part of the item opens a dropdown list #2347

Added new $method modifier to match requests by HTTP method

Reworked the rule prioritizing algorithm by adding more accurate calculation of weights for each rule type

Content scripts are injected into open tabs when the extension starts

Fixes

Scriptlets are not displayed in the request details bar of the Filtering log #2341

Cosmetic rules are not applied on tabs deactivated by Chrome Memory Saver #2342

Incorrect query parameters are inserted into the bug report #2352

Custom filters aren’t updated #2356

Filtering log does not display event types #2366

The rule editor cannot be opened as a tab in the main browser window #2379

Background tab is absent in the Filtering log #2381

The pre-compiler hints and filter list sources for Edge and Opera are incorrect #2380

Browsing Security cache is not cleared #2388

Stealth Mode and Browsing Security are applied if AdGuard protection is disabled #2389

Cosmetic rules are visible in the Filtering log, even though they were not applied #2387

Fixed handling of document requests from external workers (e.g. Chrome’s omnibox)

Fixed element collapser adding redundant styles to the element

Versions

Scriplets updated to v1.9.62

tswebextension updated to v0.3.6

We’ve discovered that extension’s “Thank you” page became unavailable in some countries. This tiny update is aimed to fix it.

In this version, we have made a few minor changes, along with updates to Scriptlets and ExtendedCss. That's all for now, but stay tuned for more updates in the future!

Changelog

Versions

Scriptlets updated to v1.9.7

ExtendedCss updated to v2.0.52

Spring is bringing refreshing updates to AdGuard Browser Extension. We've made improvements to ExtendedCss and Scriptlets, and we're gearing up for something even bigger. Stay tuned for what's next.

Changelog

Versions

Scriptlets updated to v1.9.1

ExtendedCss updated to v2.0.51

In this version we've updated Scriptlets to v1.7.13, increased the extension stability and fixed minor bugs.

In this version we've updated the Assistant module, ExtendedCss and Scriptlets to block ads even better. Besides, we've added trusted scriptlets with extended functionality to the extension.

Changelog

Updated

Assistant to v4.3.68

ExtendedCss to v2.0.26

Scriptlets to v1.7.10

This update includes some improvements that make the extension more stable.

Changelog

[Improvement] Updated ExtendedCss to v2.0.10

This AdGuard Browser extension release is minor, but it’s just as important: with each update, our extension gets better.

This small update doesn’t feature any big changes that catch immediate attention. It mostly consists of small improvements and scriptlet updates.

This release is another point on the roadmap of AdGuard Browser extension. It contains many minor changes: we improved the user interface, updated filters, translations, and CoreLibs, and fixed a few bugs. As you can see, the big journey can not only begin with small steps, but also continue with them.

Changelog

[Enhancement] UI improvements to the custom filter editor #2125

[Enhancement] Reduced intensity of backlighting when hovering over buttons and tabs #2137

[Enhancement] Improved sidebar buttons and logo layout #2150

[Fixed] The $object modifier does not work #61

[Fixed] Error cannot read properties on tatacliq.com #2187

We've just recently released AdGuard Browser extension v4.1.19 and right away we noticed one nasty bug: the number of filtering rules was displayed incorrectly after updating the filter list. So we are releasing an update with this bug fix and some minor improvements.

Changelog

[Enhancement] The selected line in the Filtering log is not highlighted after closing the request details

[Fixed] Numbers in the Statistics are too contrasting for light theme #2171

[Fixed] The number of filtering rules is displayed incorrectly when downloading/updating the filter list #2175

The new version of AdGuard Browser extension 4.1.19 is now available. Install the update — it contains several improvements and bug fixes.

Changelog

[Improvement] Added the links “Report a bug” and “Leave feedback” to General settings

[Improvement] Improved functionality of cmd+f/ctrl+f commands on the Settings and Filtering log screens #2161

[Improvement] Updated scriptlets to v1.6.39

[Fixed] Web pages are scrolled automatically when clicking “Check for filter updates” in the Firefox context menu #1645

[Fixed] The sidebar settings are located too close to each other and AdGuard logo it too small #2150

[Fixed] The “Update filters” button looks blurry and is smaller than other buttons on the extension popup #2151

[Fixed] The selected line is not highlighted on the “Details” screen in the Filtering log #2156

[Fixed] The rules for hiding elements are removed in Brave and Opera browsers #2169

We always want to make the interface even more user-friendly for you and the filtering more efficient. That's exactly what the new version of AdGuard Browser extension has to offer.

We've made a lot of fixes and improvements: for instance, we added the Update filters button directly to the extension pop-up.

Changelog

[Enhancement] Added the Update filters button to the extension pop-up #1455

[Enhancement] Improved descriptions of the Stealth mode features

[Enhancement] Some areas of the Filtering log became clickable — now it’s easy to move one step back #2134

[Enhancement] Clicking a request in the Filtering log now opens the Request details #2136

[Enhancement] The elements of Filtering log are symmetrically #2088

[Enhancement] :hover elements became less contrast in dark theme #2137

[Enhancement] Improved readability in dark theme #2139

[Enhancement] Highlighted ping type and pseudo-properties in the User rules editor

[Enhancement] Highlighted touch-action property in the User rules editor

[Enhancement] Update the translations into Croatian #2113

[Fixed] script modifier doesn't work alongside with popup modifier #1992

[Fixed] The rules with TLD (top-level domains) don't work in some cases #2037

[Fixed] The $replace rule breaks video player in some cases #2038

[Fixed] The regex filter doesn't work in AdGuard Browser extension v4.0.161 #2042

[Fixed] $match-case modifier doesn't work correctly #2049

[Fixed] Can't copy User rules in the AdGuard Browser extension for Firefox on Android 2065

[Fixed] Add permission to read and modify privacy settings when first enabling the Block WebRTC option #2074

[Fixed] $redirect-rule modifier does not work correctly #51

[Fixed] The regex rule is not applied properly #52

[Fixed] Add an empty $path variable for the main page only #54

[Fixed] Disable the Check for updates button when no filters are enabled #2108

[Fixed] Do not suggest to remove query parameters for cookie rules

[Fixed] The cursor is flashing when hovering over a row in the Filtering log table

[Fixed] The rule for hiding elements is not applied to all subdomains #57

When you use AdGuard, good news will be forthcoming. Meet the new release of AdGuard Browser extension. This version is entirely dedicated to fixing bugs which means it will improve your user experience.

For example, previously some scriptlets were displayed in the Developer Tools console even when the Filtering log was closed. Now this problem no longer exists.

See the full list of changes and upgrade to the latest version!

Changelog

[Fixed] Some scriptlets are displayed in the Developer Tools console even when the Filtering log is closed #2104

[Fixed] Align the Apple logo with the axis of symmetry #2094

[Fixed] In the Russian localization the sentences are truncated #2092

[Fixed] Increase the contrast with a light theme enabled in the Filtering log #2091

[Fixed] Align sliders in Allowlist and User rules #2089

[Fixed] Corrected the translations of the days of the week #2087

[Fixed] Make the corners of the frames equally rounded in Advanced settings #2084

[Fixed] There are no separator lines in the context menu if it's opened by clicking the icon #2079

[Fixed] The AdGuard extension icon is missing in the Firefox browser tab #2062

[Fixed] Improve window-close scriptlet — use the browser extension's API #170

[Fixed] The AdGuard extension icon is missing in the mobile version of Firefox #2032

[Fixed] Horizontal stretching in the Filtering log doesn’t work correctly #2090

[Fixed] The Filtering log is not launching #2100

[Fixed] Automatic search initiation and pop-up keyboard interfere with smooth navigation #2117

This version contains only minor fixes. But each of them has made the extension better!

Changelog

[Enhancement] Updated Tsurlfilter

[Fixed] AdGuard favicon is not displayed in the browser tab of the Firefox browser #2062

[Fixed] Syntax highlighter misses some modifiers #2075

As you can see from the changelog, this release cannot boast any epic changes: we have just fixed a few UI and UX related bugs. Nevertheless, every improvement is valuable because it brings AdGuard Browser extension closer to the ideal!

Changelog

[Enhancement] The filter log window opens with the same size, position, and state (full-screen/not full-screen) as it was when it was previously closed #1125

[Fixed] The filter name and its description are too close to each other #2022

[Fixed] The 'Preserve Log' icon becomes inactive only after double-clicking #2052

This is a minor update following the major v4.0.161 one. You probably won't know the difference but that's okay — some updates go unnoticed.

In this version we fixed a truckload of bugs, elaborated the scrollbar design, and updated translations. This update is small but efficient.

Changelog

[Added] color-scheme: dark; for post installation pages and scrolls #1408

[Enhancement] Scrollbar style #2010

[Fixed] CPU load increases on browser restart with open tabs

[Fixed] The text doesn’t fit in the button #2024

[Fixed] Filter description is too close to its title and info #2022

[Fixed] Sometimes $replace rules do not work and are not displayed in the filtering log #2018

[Fixed] Circle around the protection switch blinks when hovering the cursor over it #2015

[Fixed] Firefox Nightly error #2011

[Fixed] Phishing pop up is displayed on all websites #2009

[Fixed] Edge offers to translate the settings page into Russian although it's already in Russian #2005

[Updated] Chinese translation #2029

You’ve probably had this happen: you’re going to a party, everything seems perfect, and just before you leave you notice a stain on your clothes. What would you do? Change your look, of course. Well, we’ve noticed a little “stain” on the v4.0.133 release too: some users were unable to remove a domain from Allowlist after the update. And we’ve decided to release a new version right away with this bug fixed.

Changelog

[Fixed] Pause button not fully aligned to center #1994

[Fixed] User rules and allowlist box shrinks little to left #1995

[Fixed] Rules with :where() pseudo class do not work #1998

[Fixed] Cannot remove a domain from Allowlist after update to v4.0 #2002

[Fixed] 'Learn more' button design on update popup

The AdGuard Browser extension 4.0 is not currently available to all users. The Chrome Store has approved a new version of our extension, but a phased release process is now underway: the version will be rolled out gradually by increasing the percentage of availability to users. Other stores (Microsoft, Opera Addons, AMO) are still reviewing it. If you don’t want to wait for the new version to arrive in the store, you can download it from GitHub.

Meet AdGuard Browser Extension v4.0! It’s not a mere update, but a major release that delivers a pack of new features to the users of the extension.

Code refactoring and new filtering engine

Refactoring has become sort of a buzzword that implies massive code rewriting, which we did to complicate our lives and make it easier in the long run. Besides, we added support for TSUrlFilter, our new filtering platform that implements AdGuard content blocking rules.

TSUrlFilter is a filtering engine. In AdGuard apps, its role is performed by CoreLibs, and if happen to read release notes, you must have heard about it more than once. TSUrlFilter is a rule application module that will be used in various projects, including AdGuard DNS.

Responsive design

We switched to responsive (or adaptive) design. That is to say, that interface elements will adapt to screen size both on desktop and mobile devices, regardless of the model.

This is convenient both for us, because we don't need to develop separate versions of the Browser extension, and for users — it's always nice when an app (or a browser extension, in the case given) looks good.

Redesign and new Filtering log

Now the filtering log not only сomplies with the principles of the responsive web design, its overall appearance has changed significantly. If you used the former filtering log, you'll be able to tell the difference: the new version presents searching in tabs, many new request statuses and filters that facilitate finding the needed requests. New filters and statuses are highlighted, and tooltips explaining each one pop up when hovering a cursor over them. Apart from that, you can preview requests and format them in the same dialog — clicking the "Beautify" button makes it easier to read these requests.

The editor in the User rules section can now be opened in fullscreen mode, which makes working adding, editing, and deleting filter rules much more convenient. Finally, there is a new action on the AdGuard Browser Extension popup that allows to reset all the user rules for the currently opened website in one fell swoop.

Besides, now the AdGuard Browser Extension features dark theme that everybody loves so much.

Support for new modifiers after switching to TypeScript

"What makes TSUrlFilter better than the previous filtering engine?" the most curious may ask. Probably, the main advantage is support of some new modifiers: $removeheader, $redirect-rule, $ping, $path, $noop, and $denyallow. And the $redirect modifier has been significantly improved, so now all the $redirect rules for a website can be cancelled by applying @@||example.org^$redirect.

In this version we've fixed only one, but nevertheless important issue.

Changelog

[Fixed] Do not accept CSS rules with "image-set" #1920

We considered the latest update to be the last before the big 4.0 release. Well, we were wrong. Here is the last one (hopefully): some minor changes and scriptlets updates. Soon you all will become witness to something really epic!

This is the last update before the big 4.0 release coming this November. Wait a bit more and you’ll see how many changes it brings.

Changelog

[Enhancement] Scriptlets updated

[Enhancement] Minor fixes

Psst, here is a BTS promo in the latest version of the AdGuard Browser Extension. Get yours updated! Don’t get overexcited though, BTS here stands for “back to school” and not what you thought, but it’s still cool, right?

This release is a hotfix for an issue that came up with the previous release.

Changelog

[Fixed] $removeparam modifier must not remove search params from POST requests #1812

AdGuard Browser Extension v3.6.5 is released.

We’ve added support for the $removeparam modifier which allowed us to get rid of the old Remove tracking parameters setting and add a new one that enables AdGuard URL Tracking filter. This will make deleting tracking parameters more flexible, so that everybody can create $removeparam user rules for their needs.

Moreover, in addition to “Do-Not-Track”, another signal appeared in the Stealth Mode settings — “Global Privacy Control”. These signals are sent to the websites you are visiting not to track you and to hide your search queries. Finally, we’ve added the birthday promo to the extension — AdGuard turns 12 on June 1!

Changelog

[Added] $removeparam modifier support

[Added] Global Privacy Control signal in Stealth Mode

[Added] AdGuard URL Tracking filter

[Enhancement] Generic CSS exclusions disable matching CSS/elemhide rules on all domains #1801

[Enhancement] CSP reports to third parties and csp-reports containing moz://extension are blocked #1792

[Enhancement] Updated Scriptlets and redirects from v1.3.15 to v1.3.18

[Enhancement] Updated ExtendedCss from v1.3.10 to v1.3.11

[Enhancement] Portuguese and Portuguese Brazilian localizations are updated following the Portuguese Language Orthographic Agreement of 1990

Note: In progress on Chrome Store review.

Another small but important… Oh please, spare me this. The extension looks a bit brighter now that we have an Easter promo. And of course, the new version includes a basic starter pack of each release, big or small: we’ve updated filters, extended CSS to v1.3.10, scriptlets — to v1.3.15, and AdGuard Assistant — to v4.3.45. These are small preparatory steps for the coming update. Trust us, it’s going to be epic.

A small but important release. We’ve added a new pseudo-class :is() and upgraded extended CSS to v1.3.8. :is() is a CSS pseudo-class function that comes in handy for writing large selector lists more compactly. Now AdGuard AdBlocker extension supports this functionality.

Another brick in the wall: building our perfect browser extension. It seems that the few latest updates passed without notice – it’s no wonder ’cause we didn’t show to users any visible change. Yet, don’t let yourself be disappointed with the same old mantra: Scriptlets, Extended-CSS, and filters. They matter. So, we’ve updated Scriptlets to v1.3.13 and Extended-CSS to v1.3.6. AdGuard Assistant has been updated to v4.3.37. Plus, we’ve added new translations and filters to this version.

When you're on a journey to the perfect ad blocker, every step matters. Even if it's on the smaller size like today: in this update, we only touched on scriptlets and extended CSS optimization.

The new version of AdGuard AdBlocker extension has been released. We’ve updated the scriptlets, locales, and extended CSS — and that’s just the tip of the iceberg. This beta harbours many secrets: many changes remained under the hood, but rest assured, they will improve the app’s performance.

Changelog

[Enhancement] Scriptlets have been updated to v1.3.6

[Other] Localization issue #1678

The release of AdGuard AdBlocker extension v3.5.12 was preceded by four betas the version numbers of which look like Fibonacci sequence: 3.5.3, 3.5.5, 3.5.8 (and 3.5.12 falling out of line)… Seems like we’re getting close to the golden ratio! We hope that you’ll find the changes we made to the extension beautiful and well calibrated.

Changelog

[Enhancement] Integration mode has been removed

[Enhancement] Filters metadata has been updated

[Enhancement] Scriptlets have been updated to v1.3

[Enhancement] Improved google-analytics and googlesyndication-adsbygoogle support #67, #91

[Enhancement] Added :upward support #102

[Enhancement] Added :remove() support #108

[Enhancement] Changed restrictions for CSS injection rules with \ character #1614

[Enhancement] All requests initiated by the browser extension have been sanitized #1647

[Enhancement] Changed the way Safebrowsing lookup API works #1648

[Fixed] Error with set-constant caused by non-existent chain property

[Fixed] adguard.configure callback does not apply rules #1607

[Fixed] Some requests blocking rules don't work correctly #1620

[Fixed] Cosmetic rules can be used as CSS rules #1624

[Fixed] Triggered scriptlet rules without domain restrictions are not displayed in filtering log #1637

[Fixed] Infinite pending request status on some web pages #1644

[Fixed] AdGuard v3.5 is not working on Firefox v54 and below #1674

[Other] Thai localization has been added #1590

In this small hotfix we update scriptlets and related metadata.

[Changed] Scriptlets have been updated to v1.1.13

[Changed] Scriptlets’ metadata has been updated

This is a small update that fixes a few ad blocking- and networking-related bugs, as well as introduces some other minor improvements in UI and other areas.

Ad Blocking

[Added] $ping modifier support #1584

[Fixed] Rules are not applied to websites with dot at the end of their domain name #1586

[Fixed] $3p,domain= rule works as CSP rule #1585

[Fixed] $badfilter modifier doesn't work correctly together with $all modifier #1573

[Fixed] max-length set to 256KB for ##^ rules #1556

[Fixed] Element hiding gets broken by an invalid element hiding rule #1554

[Improved] $domain modifier semantics #1534

[Improved] More modifiers’ aliases have been added #1592

UI

[Fixed] “User rules” highlighting issue #1581

[Improved] Enabled filters have been moved to the top of the list #1259

Networking

[Fixed] Manual element blocker doesn’t work on a website #1540

[Fixed] Enabling “Send ad filters usage stats” breaks webpages on Edge Chromium #1561

Other

[Added] Handling of the adguard:subscribe protocol for installing new filter subscriptions #1447

[Changed] “About” tab and the Settings footer have been updated #1579

[Changed] Update scriptlets to v1.1.9

[Fixed] Exporting/importing the whitelist creates duplicate entries #1531

[Fixed] Rules added via Filtering log are not visible in the already opened Filter editor #1410

[Fixed] Scriptlets are not validated before execution #1593

[Improved] Accessibility for visually impaired users #1456

Fixed an issue with AdGuard add-on running upgrade script even when the add-on was not actually updated.

A small update to enter the new year with a little bit less bugs :)

[Added] Default filters update period #1549

[Changed] Update localizations #1550

[Changed] “Get AdGuard for your mobile" has been hidden from the browser action on MS Edge #1543

[Fixed] Exception rules with $popup modifier don't work #1542

[Fixed] Stealth Mode accepts empty field as a valid value for cookies’ self-destruction time #1544

[Improved] Scriptlets library has been updated to v1.1 #1548

Today’s update is something in-between a hotfix and a regular release. It lacks in numbers of changes compared to some other versions, but isn’t a hotfix either as we don’t patch any specific bug. All in all, consider it a quality of life update.

[Added] Estonian and Hindi localizations #1497

[Changed] “AdGuard” to “AdGuard” in devtools browser tab #1509

[Changed] An $important modifier is now added when creating an exclusion for a rule with $important#1516

[Fixed] Sometimes rules with $popup modifier don’t close popup windows #1519

[Fixed] Extra empty lines are added when pasting rules into the Filter editor #1517

[Fixed] Safebrowsing alert page is displayed in wrong language #1510

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

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

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.

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

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.

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

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

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

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

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

افزونه مرورگر AdGuard – Release – نسخه های AdGuard

Changelog

Fixes

Changelog

Changelog

Improvements

Changelog

Fixes

Custom filters

Update checks

Blocking page

Design improvements

Changelog

Improvements

AGTree (A tool for working with adblock filter lists)

AdGuard Logger (A tool for logging from AdGuard extensions)

Scriptlets (JavaScript enhancement for filtering rules)

TSUrlFilter (AdGuard Browser Extension filtering engine)

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

Fixes

Changelog

Fixes

Changelog

Improvements

AGTree (A tool for working with adblock filter lists)

TSUrlFilter (AdGuard Browser Extension filtering engine)

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

Changed

Changelog

Improvements

Fixes

AGTree (A tool for working with adblock filter lists)

Scriptlets (JavaScript enhancement for filtering rules)

TSUrlFilter (AdGuard Browser Extension filtering engine)

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

Changelog

Removed

Changelog

Changed

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

Removed

How to install MV3 stable:

How to install MV3 beta:

Changelog

Changed

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

Removed

How to install MV3 stable:

How to install MV3 beta:

Changelog

Improvements

Fixes

AGTree (A tool for working with adblock filter lists)

TSUrlFilter (AdGuard Browser Extension filtering engine)

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

Changelog

Fixes

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

Changelog

Fixes

Changelog

Fixed

AdGuard Logger (A tool for logging from AdGuard extensions)

TSUrlFilter (AdGuard Browser Extension filtering engine)

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

Changelog

Fixes

AdGuard Logger (A tool for logging from AdGuard extensions)

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

Changelog

Fixes

AdGuard Logger (A tool for logging from AdGuard extensions)

TSUrlFilter (AdGuard Browser Extension filtering engine)

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

Changelog

Scriptlets (JavaScript enhancement for filtering rules)

TSUrlFilter (AdGuard Browser Extension filtering engine)

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

Changelog

Fixes

Scriptlets (JavaScript enhancement for filtering rules)

The new `tswebextension` library