We're in no hurry to move to MV3 right away as its API is very limited.Īdding 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. With MV3, we need to maintain filter 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. A Chrome- and Firefox-specific programming interface responsible for applying the rules found.A filtering engine that matches URLs with the rules loaded into it.The main purpose of the library is to reuse the filtering logic in our products (browser extensions for Chrome and Firefox, rules converter for Safari, linter, etc.). Some time ago we transferred the URL filtering engine from the extension to a separate library called `tsurlfilter'. We've moved all the “filtering” code into a new, separate library - this allows us to prepare the extension for a seamless transition to MV3. The new version of AdGuard Browser Extension has undergone major changes that are not immediately noticeable.

Firefox adguard