How will Vivaldi deal with Google's Manifest V3?

kirill1996

Manifest V2 in Vivaldi, when does it stop working?
How do you plan to continue releasing updates for the browser, if, soon, there will be a transition to extensions for Chrome (Chromium) on Manifest V3?

superiorclam

@kirill1996 said in Manifest V2 in Vivaldi, when does it stop working?:

Manifest V2 in Vivaldi, when does it stop working?
How do you plan to continue releasing updates for the browser, if, soon, there will be a transition to extensions for Chrome (Chromium) on Manifest V3?

Please see https://forum.vivaldi.net/topic/93057/how-will-vivaldi-deal-with-google-s-manifest-v3/

DoctorG

@kirill1996 End is in June 2025.
There is no chance to extend this for Vivaldi dev team.

kirill1996

@DoctorG said in Manifest V2 in Vivaldi, when does it stop working?:

There is no chance to extend this for Vivaldi dev team.

Brave said they would support it.
Why can't they copy code from Github to Vivaldi, yours?

DoctorG

@kirill1996 said in Manifest V2 in Vivaldi, when does it stop working?:

Brave said they would support it.
Why can't they copy code from Github to Vivaldi, yours?

I have no knowledge why this can not be added.

RasheedHolland

@DoctorG said in Manifest V2 in Vivaldi, when does it stop working?:

@kirill1996 End is in June 2025.
There is no chance to extend this for Vivaldi dev team.

I'm sorry, but this sounds a bit misleading. Of course there is a chance that Vivaldi could extend support for MV2, similar to Brave, Opera and Firefox. The question is, do they WANT to do this or not?

rseiler

@DoctorG Probably not that promptly due to Vivaldi using the extended stable channel of Chromium. I bet more like in August for us.

barbudo2005

Just to clarify, Firefox uses another core so it is not affected by the change between MV2 and MV3.

barbudo2005

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.

npro

@rseiler said in Manifest V2 in Vivaldi, when does it stop working?:

@DoctorG Probably not that promptly due to Vivaldi using the extended stable channel of Chromium. I bet more like in August for us.

Not quite, basically ~2 weeks after the Chromium 138 release on 24 June.

rseiler

@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.

npro

@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?

RasheedHolland

@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.

RasheedHolland

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?

CummingCowGirl

@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.

RasheedHolland

@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.

DoctorG

@RasheedHolland

'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.

DoctorG

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.

CummingCowGirl

@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.

DoctorG

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.
— Source

And blogs tells you more: