- Jan 6, 2022
- 558
Using uBO Lite with Edge myself, but I think the people at AdGuard are very creative in finding solution to work around some of the limitations of MV3. IMO that is not a bad thing and could possibly be used by other adblockers.I was always skeptical about Adguard using all these gimmicky workarounds to MV3's limitations. The problems they keep encountering confirms this. Best bet is to use Firefox with µBO or Brave.
![]()
What happened to Custom filters and Quick Fixes filter
Chrome’s policies forced us to remove important features from the MV3 extension. We’re already working on solutions: you can find more details in this post.adguard.com
I agree. Google is the one who's changing things and good to see that the AdGuard team is finding their way around some of the limitations. Some of the changes made by Google is actually good for security but I also believe that weakening adblockers was also one of their motives behind MV3.Using uBO Lite with Edge myself, but I think the people at AdGuard are very creative in finding solution to work around some of the limitations of MV3. IMO that is not a bad thing and could possibly be used by other adblockers.
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.
It seems that after the death of Quick fixes filter, they are now trying to release a new version of the extension every 3 days. It's good if they can keep up the pace.
How we are solving this
We’re overhauling how AdGuard handles filtering rules to comply with Chrome’s policies while keeping the extension functional and useful.
Here’s what we’re doing:
- To bring back Custom filters, we’ll use the userScripts API. This API lets us register scripts in a way that complies with MV3 policies.
However, there’s a catch: users will need to enable Developer mode to use them, which adds an extra step. We know this might be a barrier for less tech-savvy users, so once we roll out the version with custom filters, we’ll make sure to provide clear instructions on how to enable it and add filters.- Since the Quick Fixes filter can no longer exist in its original form, we’re switching to Chrome’s fast-track review process. This will allow us to update filters more frequently without waiting for a full extension review. However, this method has some limitations: it only applies to changes in DNR rulesets and safe rules.
We’ll soon have two types of extension updates: fast-track updates — set to happen automatically every few hours, and full updates — with a review in the Chrome Web Store.
Requiring the use of developer mode is such an example. Pure security risk.I was always skeptical about Adguard using all these gimmicky workarounds to MV3's limitations. The problems they keep encountering confirms this.
This is required even to run userscripts in extensions like Tampermonkey. I use 7 userscripts (currently in Edge with Violentmonkey MV2) and 5 of which are a must for me (YouTube related) but on MV3 Tampermonkey, I need to enable Developer mode for them to work. Letting an extension secretly loading a third-party script from the web is a security risk indeed (Firefox never allowed it) but now they don't even allow it by default in userscript extension where users by their own will install scripts. Even with developer mode they work like sh*t. Multiple scripts are not executed 8/10 times for me. The MV3 userscript API has bugs and limitations and Google have no rush to fix anything.I'll say it again
Requiring the use of developer mode is such an example. Pure security risk.
Indeed, Google's failure to address its own issues is what make these extensions inherently unreliable in carrying out more than simple functions.he MV3 userscript API has bugs and limitations and Google have no rush to fix anything.
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!