Vivaldi does a lot of adblocking natively, and they are maintaining V2 as long as they can, which based on info from Google is summer 2025 but might change.
Yes but that doesn’t change the fact that in 10mo uBlock origin won’t work on Vivaldi. The perils of chromium builds. I don’t blame Vivaldi, I’m just stating a fact. They won’t support Mv2 and uBlock origin will not work.
Could we keep using our ad-blocking extensions in Vivaldi?
But, “Wait”, I hear you say, “Doesn’t that mean that basically, Vivaldi might be able to keep webRequest intact just by bypassing the checks for enterprise environments? Could we keep using our adblocking extensions in Vivaldi?”
This certainly sounds plausible, but it is not something that we can promise without seeing what ends up happening in the code itself. If there is an easy way to keep webRequest functioning as it did for a while longer, we’ll consider doing it.
However, it is important to note that extension ad blockers often depend on other APIs that are removed in Manifest V3 (and probably much harder to bring back), so there is no guarantee that simply keeping the blocking version of webRequest alive is going to be enough, without some work from extension maintainers.
Vivaldi does a lot of adblocking natively, and they are maintaining V2 as long as they can, which based on info from Google is summer 2025 but might change.
Yes but that doesn’t change the fact that in 10mo uBlock origin won’t work on Vivaldi. The perils of chromium builds. I don’t blame Vivaldi, I’m just stating a fact. They won’t support Mv2 and uBlock origin will not work.
Will the Vivaldi Ad Blocker be affected by the Manifest V3 changes? I made some architectural choices early on that I believe should keep it functional, regardless of the Manifest V3 changes.