How will Vivaldi deal with Google's Manifest V3?
-
@npro If 138 is the first one without it. What if it's the last one with it? I'm not sure if they've clarified that yet. If it's the latter, then we would be talking more like August.
-
@rseiler said in How will Vivaldi deal with Google's Manifest V3?:
What if it's the last one with it?
I don't think so, they said that "enterprises will have one additional year (starting from June 3, 2024) - until June 2025 - to migrate the Manifest V2 extensions in their organization." , meaning starting with July 1 (the latest) MV2 will not be supported anymore and you should be ready for it. Support for Chrome 137 ends in June 24, so this means you should be ready for July (in reality for June 24+) with Chrome 138 (being the only version supported in that period), where MV2 won't work. Besides, how does this matter to you, won't you be still using Vivaldi anyway?
-
@barbudo2005 said in How will Vivaldi deal with Google's Manifest V3?:
Just to clarify, Vivaldi is not willing, does not want, is not interested, is not in the mood, is not willing to spend those scarce human resources forever, let's see how I put it so that it is well understood and once and for all.
Where did you read this stuff? And if true, then I predict that a lot of people will switch from Vivaldi to Brave, Opera and Firefox. So Vivaldi might want to reconsider, if what you're saying is true.
-
By the way, I noticed that in Viv 7.3, you now all of a sudden have to enable ''developer mode'' in order to make certain extensions work, because they can't be reviewed by the Chrome Web Store? And I'm also getting to see a message that certain extensions soon won't be supported anymore. I didn't get to see this crap in Viv 7.2. So is the solution to simply enable ''developer mode'' in order to make MV2 extensions work?
-
@RasheedHolland said in How will Vivaldi deal with Google's Manifest V3?:
solution to simply enable ''developer mode'' in order to make MV2 extensions work?
That's a temporary solution at best. Real solution is to look at the ones that have not ported over yet and hound the developers. At least With Chrome the developers have more than ample warning and time unlike when Mozilla suddenly switch engines for their extensions and told no one in advance.
-
@CummingCowGirl said in How will Vivaldi deal with Google's Manifest V3?:
That's a temporary solution at best. Real solution is to look at the ones that have not ported over yet and hound the developers. At least With Chrome the developers have more than ample warning and time unlike when Mozilla suddenly switch engines for their extensions and told no one in advance.
The problem is that certain extensions may not be updated anymore, because they are no longer being developed. And we already talked enough about how uBlock Origin is way superior over uBlock Lite and other adblockers.
So Vivaldi should find a way to keep supporting MV2 extensions, if possible without having to keep developer mode enabled. I'm surprised that Vivaldi stays quiet over this issue, while Brave, Opera and Firefox have all said to keep supporting MV2.
-
'm surprised that Vivaldi stays quiet over this issue, while Brave, Opera and Firefox have all said to keep supporting MV2.
Brave said, that does not support Mv2 completely. Hwo this affects some extensions, i do not know. Brave users need to test it themselves.
And if that is really a true long-term support for Brave and Opera, we will see after June 2025. -
I think if there would be a easy fix to get Mv2 working in newest Chromium core for Vivaldi, the devs would have added one.
If Brave and Opera can support Mv2 until the next decades, they have more humanpower in development team and more money to spend on such patches.
-
@RasheedHolland said in How will Vivaldi deal with Google's Manifest V3?:
So Vivaldi should find a way to keep supporting MV2 extensions, if possible without having to keep developer mode enabled. I'm surprised that Vivaldi stays quiet over this issue, while Brave, Opera and Firefox have all said to keep supporting MV2.
It's not a matter of Vivaldi keeping quiet but rather they have repeatedly covered what their plans are. Anyone doing a proper forum search would know that.
-
I do not know why this is endlessly discussed if Vivaldi will keep Mv2.
We will keep Manifest v2 for as long as it’s still available in Chromium.
— SourceAnd blogs tells you more:
-
Said:
I do not know why this is endlessly discussed if Vivaldi will keep MV2.
Don't you understand? It's crystal clear. There is a user who:
- Is not willing to understand
- Does not want to understand
- Is not interested to understand
- Is not in the mood to understand
- Is not willing to spend 5 minutes to read the posts
Let's see how I put it so that it is well understood and once and for all.
-
@barbudo2005, are there browsers which support still Mv.1? (asking for an Friend)
-
@DoctorG said in How will Vivaldi deal with Google's Manifest V3?:
I do not know why this is endlessly discussed if Vivaldi will keep Mv2.
@barbudo2005 said in How will Vivaldi deal with Google's Manifest V3?:
Don't you understand? It's crystal clear.
@CummingCowGirl said in How will Vivaldi deal with Google's Manifest V3?:
It's not a matter of Vivaldi keeping quiet but rather they have repeatedly covered what their plans are. Anyone doing a proper forum search would know that.
That is a blogpost from 2,5 years ago. You would think by now that Vivaldi has more information on how they will handle this, that's all I'm asking. Like I said, from a technical point of view, it should be possible to keep supporting MV2, that's what Opera, Brave and Firefox are planning to do.
I'm not sure how much manpower is needed to patch Chromium. If you read the article, you can clearly see that Vivaldi might try to keep supporting MV2, which means that Vivaldi's built-in adblocker won't be affected. But in theory this means that MV2 extensions might still be able to work. That's what you guys refuse to understand.
https://vivaldi.com/blog/manifest-v3-webrequest-and-ad-blockers/
-
-
@RasheedHolland said in How will Vivaldi deal with Google's Manifest V3?:
If you read the article, you can clearly see that Vivaldi might try to keep supporting MV2, that's what you guys refuse to understand.
For me that reads (sorry, my restricted english practising): "we try to support Mv2 but can not guarantee that we get a workaround."
But, who knows, in next months we might get a 7.999 Stable or 8.0 Beta which saves us from Google forcing Mv3.
-
@DoctorG said in How will Vivaldi deal with Google's Manifest V3?:
For me that reads (sorry, my restricted english practising): "we try to support Mv2 but can not guarantee that we get a workaround."
But, who knows, in next months we might get a 7.999 Stable or 8.0 Beta which saves us from Google forcing Mv3.
Nowhere in this article it's said that Vivaldi has no interest in supporting MV2 extensions. In fact, it's said that they still need to see how exactly this MV3 API removal will play out. But I'm sure that by now Vivaldi has got more info about this, since Google is planning to remove support for MV2 in June 2025. And again, if Brave and Opera can patch Chromium, so can Vivaldi.
In the comments you can also see certain suggestions from users, like the ability to side load extensions from GitHub, so you don't even need the Chrome Web Store. And some user suggested that Vivaldi can perhaps simply copy uBlock Origin features. But not a word from Vivaldi since this post of 2,5 years ago. So it's not weird that users keep discussing this issue.
-
@DoctorG said in How will Vivaldi deal with Google's Manifest V3?:
For me that reads (sorry, my restricted english practising): "we try to support Mv2 but can not guarantee that we get a workaround."
But, who knows, in next months we might get a 7.999 Stable or 8.0 Beta which saves us from Google forcing Mv3.
And of course I forgot to mention this article from 9 months ago, which is also a longtime ago, where it's said ''they may or may not keep supporting MV2 for a longer time.'' So I'm asking for more clarity in a way that Brave, Opera and Firefox have done, that's all. Nothing more, nothing less.
-
@RasheedHolland, sooner or later, all are going to stop the support for Mv2, just as left in the past, they left the support of Mv1.
No many devs can keep the development of extensions for Mv2 and Mv3 - especially with the different management of cookies in web pages, at least those which use Google APIs (sadly the most) that invalidates Mv2.Google - The Ring which rules them all, browsers only can limit the damage, irrelevant which browser or engine.
-
@RasheedHolland said in How will Vivaldi deal with Google's Manifest V3?:
And of course I forgot to mention this article from 9 months ago, which is also a longtime ago, where it's said ''they may or may not keep supporting MV2 for a longer time.'' So I'm asking for more clarity in a way that Brave, Opera and Firefox have done, that's all. Nothing more, nothing less.
You dropped the part where it says,
We expect to drop support in June 2025, but we may maintain it longer or be forced to drop support for it sooner, depending on the precise nature of the changes to the code.
So, everything depends on upcoming Google code. Do you really expect each and every Chrome based Browser to maintain a seperate own Store for MV2 Addons? The Addon devs surely don't want to work for each seperated store, just to satify your greed. From where else do you get these abandoned Addons for a reinstall? Firefox is another case, based on it's own browser engine.
For my part, I wait what comes out of all this manifest mess. What I really miss in MV3 Adblockers is a whitelist button, so I don't have to put each site onto the whitelist manually.
-
@wolden, it' not depends only the Webstore, if they offer Mv2 extensions, when most webpages include Google APIs which invalide Mv2 extensions.
* 
