While blocking extensions won’t go away, there will be limitations. If you only use one extension, for example to stop seeing ads, you shouldn’t notice anything. However, if you like to use custom filter lists or use multiple extensions based on the Extensions API, you might run into the limits set by Google. What this will look like in practice remains to be seen in each individual case. AdGuard recently released a Manifest v3 compatible ad blocker that displays warnings when its functionality is restricted in the browser. Mozilla also announced that it will generally support Manifest v3. However, a fallback option to Manifest v2 is also available in Firefox. This should ultimately ensure, among other things, that uBlock Origin, which is popular with Firefox users, continues to work smoothly – as this should no longer be the case in v3. In the Chrome universe, extensions must support Manifest v3 from January in order to be referenced in the Chrome Web Store, for example. Starting in June, Manifest v2 extensions will no longer be supported in the browser at all. This applies to Chrome and all other Chromium-based products, like Microsoft Edge.
Firefox could soon gain a competitive advantage that Google is ultimately responsible for. Because market leader Chrome will only support some content blocking extensions to a limited extent in the future. Starting next year, extensions for Google Chrome and most other Chromium-based browsers will rely on a new extension manifest. This defines the limits within which extensions can operate. Google will use its dominant position in the browser market to pass Manifest v3, that is to say the 3rd version. This also includes restrictions on extensions used to block various types of content. The most common variation here is ad blocking, but many users also use similar technologies to block certain scripts or other code that could pose potential security risks, according to a report by Ghacks.