Adguard extension 2.8 update#

With tswebextension, it will be easier to maintain and update our products. The new library was named tswebextension. 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 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. A Chrome- and Firefox-specific programming interface responsible for applying the rules found.A filtering engine that matches URLs against 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, rule converter for Safari, linter, etc). Some time ago, we moved the extension's URL filtering engine into a separate library called tsurlfilter. You can read more about Chrome’s limitations and how we tried to adapt to them in the world’s first ad blocker built on Manifest V3.

Among other things, it will make it significantly harder for browser extensions to block ads by limiting the number of filtering rules they can apply. Manifest V3 (MV3) is Chrome’s new extension API. 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. The new version of AdGuard Browser Extension has undergone major changes that are not immediately noticeable.

Adguard extension 2.8