How will Vivaldi deal with Google's Manifest V3?
-
@stardepp Well, it says so right in your image how you call the command
https://www.wikihow.com/Open-the-Command-Prompt-in-WindowsWhat do YOU get?
🎻Volunteer helper · Forum moderator · Sopranos tester 🛠️Troubleshooting 🐛Report a bug 📜Markdown help
🦆"With a rubber duck, one's never alone" -Douglas Adams🦆 -
@Pathduck I would very much like to know if the “Stylus” expansion will support Manifest 3. This is my most important expansion.
🍀 Before you ask, use Vivaldi Help (F1🍀Search Engine Collection🍀My Themes🍀Windows11 24H2 *Samsung A54 Android14🍀
-
@stardepp The best way is to check the code repo.
https://github.com/openstyles/stylus/blob/master/manifest.json
Still on v2.
So get involved I guess. But looksl like it's regularly updated and under active development so should be no problem.
https://github.com/openstyles/stylus/issues -
@ybjrepnfr said in How will Vivaldi deal with Google's Manifest V3?:
@Catweazle said in How will Vivaldi deal with Google's Manifest V3?:
FF also will change to Mv3
you keep repeating this fallacy. it's like you're deliberately trying to misdirect people, for goodness sake. mozilla have stated & restated that they are incorporating mv3 for ongoing compatibility BUT [& you keep ignoring this vital part] it is to complement their existing & ongoing mv2 capability, not replace it.
Without Facepalming, at the moment FF will support Mv2 and Mv3 until FF128, but it's working to migrate sooner or later to Mv3. Which is also logical, since otherwise it would force developers to work on two versions of their extensions.
Mv3 is the standard in the future, yes or yes. Possibly Mozilla supports Mv2 longer than Google, because of the limitations of Chromiums depending on the Chrome Store, but surely not indefinitely.
At the moment Vivaldi, like FF will support Mv2 until the timeout in June 2025, later, we'll see. Mozilla said that it will announce the change before, to give enough time to the devs of the extensions to migrate.
https://blog.mozilla.org/addons/2024/06/13/manifest-v3-updates-landed-in-firefox-127/
-
I do not think Mozilla will support Mv2 many years.
The Mozilla dev team decide what they will use as a Standard.
Perhaps they will give users a special enterprise ESR (LTS) version which will have Mv2 for a longer time. -
@DoctorG, that is the point, for Vivaldi it simply won't make sense to support Mv2 after Google discontinued this extensions in the Chrome Store, because of this Mozilla has somwhat more time for the change with the own Store.
But the question is if it make sense for the devs to support much time two versions of their extensions for an minority browser, instead of going direct to v3.
On the other hand, in extensions not related to privacy and security, like Dark Readr, Translation tools, etc. it's irrlevant if they are Mv3 or not. That means, Vivaldi has to go independient from the Chrome Store with inbuild features related to privacy and security.
>Laptop Lenovo V145 15AST, AMD A9- 9425 Radeon R5 - 5 cores 3,1 GHz RAM 8GB, GPU 2+1 GB SSD 256GB -Win10 64 v22H2| Vivaldi last stable|
-
As always with your posts, it is necessary to clarify and refute them so that less informed users are not influenced:
Said:
,,, at the moment FF will support Mv2 and Mv3 until FF128...
As the Mozilla link you posted says:
The team will land more Chrome compatibility enhancements in Firefox 128...
It does not say FF will support Mv2 until FF128.
What it does say and reiterates is:
Mozilla has no plans to deprecate MV2
Said:
At the moment Vivaldi, like FF will support Mv2 until the timeout in June 2025, later, we'll see.
1.- Vivaldi is not doing anything to keep MV2 running from June 2024 to June 2025 for some users who have not applied the policy, and certainly to June 2025 for those who did apply it.
It all depends on Google as seen in the Chromium I have installed in which uBO is working without problems.
2.- With respect to "later, we'll see" the thing is clear:
a) In Vivaldi it will not be possible to use extensions other than MV3 after June 2025.
b) Mozilla says repeatedly that it has no intention to remove the support to MV2, and as June 2025 is a relevant milestone, it is understood it will be extended after June 2025. What we do not know and therefore we cannot speculate is how long it will last.
Said:
for Vivaldi it simply won't make sense to support Mv2 after Google discontinued this extensions in the Chrome Store...
Again, a clarification:
Vivaldi will not support MV2 because it is simply a huge job and he does not have the resources to do it.
And it has nothing to do with the fact that the extensions will not be in the Chrome store, since they can be loaded from other sites.
It seems that @ybjrepnfr is basically right, in that your conscious or unconscious objective is to spoil the party for those users who are going to switch to Firefox.
Finally, I ask you not to answer this post, because as it always happens every time you try to clarify a post the only thing you achieve is to obscure the subject.
-
Said:
I would very much like to know if the “Stylus” expansion will support Manifest 3.
In this post "Switch to manifest v3 #1430" tophf (the author) in June 14 said:
That's completely unusable i.e. I don't see the point of maintaining Stylus if that's how it has to work. Also, many sites open within 100ms, especially those that have a service worker installed e.g. telegram may start opening (onCommitted) in 30ms since the earliest moment the URL becomes known (onBeforeRequest).
It'd be especially bad when navigating the same site with a style that applies differently depending on the page URL because pages could be loaded very fast and they look similar, so hiding the old contents would be very disruptive and ugly.
I guess I'll try userScripts permission, which is the only reliable solution in ManifestV3, but a) its implementation in Chrome is irrationally dependent on the devmode switch and b) it may be disallowed in the web store since our extension's purpose is not userscripts, c) it's wasteful in regards to the regexp as I explained in my previous comment.
Said:
So get involved I guess. But looks like it's regularly updated and under active development so should be no problem.
Undoubtedly he is studying the subject in depth, as you can see in the post.
Let us hope that the saying “No news good news” is true in this case.
-
@stardepp said in How will Vivaldi deal with Google's Manifest V3?:
@Pathduck I would very much like to know if the “Stylus” expansion will support Manifest 3. This is my most important expansion.
Well, I haven't read whole of the thread, but I just saw (when I upgraded to Viv 6.9) that certain of my extensions will possibly not work because they are still MV2 based, so it would be nice if Vivaldi would keep supporting MV2 for as long as possible, similar to Brave. The problem is that some extensions are no longer maintained.
-
@RasheedHolland, Vivaldi will support v2 as long as possible, but after June 2025 or earlier, Mv2 extensions are not longer available in the Chrome Store and because of this Mv2 extensions which you are using from the store are getting desactivated.
-
@Catweazle said in How will Vivaldi deal with Google's Manifest V3?:
@RasheedHolland, Vivaldi will support v2 as long as possible, but after June 2025 or earlier, Mv2 extensions are not longer available in the Chrome Store and because of this Mv2 extensions which you are using from the store are getting desactivated.
Yes correct, I understand that this is the problem. But perhaps Vivaldi can open a website where certain MV2 extensions can be downloaded from. I believe Opera and Edge have their own extensions store.
-
Said:
...so it would be nice if Vivaldi would keep supporting MV2 for as long as possible…
From what I understand, the team is not "supporting" MV2. It all depends on Google.
As you can see in the image of Chromium without having applied the policy in the registry, it shows these extensions working, but that “soon” they will stop doing so.
Whereas on my Vivaldi, to which I apply the policy, no such message appears:
Explanation of “soon”:
1.- If you applied the register policy, “soon” means after June 2025.
2.- If you not applied the register policy, “soon” means between June 2024 and June 2025.
-
@RasheedHolland, naturally you can add extensions from other sources, but also the support of Mv2 will end in Vivaldi and other Chromium, also in Edge, Opera and Brave, so they can't not longer use these.
-
WTF! Google!!1!11!! The worst thing Google tells me now and hitting on my hands to throw away needed work tools.
There are no Alternatives!Only Alternative would be Mozilla
_bug hunter · Volunteer helper · Sopranos tester · Language DE,EN
Known old dragon lady: Gwen aka Dr. Gwen Agon aka GwenDragon aka DoctorGTesting
Linux Debian 12 KDE X11 / Windows 11 Pro
Intel i5-7400 / NVidia GT 710 -
@Catweazle said in How will Vivaldi deal with Google's Manifest V3?:
@RasheedHolland, naturally you can add extensions from other sources, but also the support of Mv2 will end in Vivaldi and other Chromium, also in Edge, Opera and Brave, so they can't not longer use these.
Yes good point, so that's why I keep repeating that Vivaldi should open its own extension store and keep supporting MV2 by making changes to Chromium. Either this, or they should implement certain features, but I doubt they will integrate stuff like video downloaders.
However, certain features like adblocking, picture resizing and automatic tab stacking are basic browser features, this should be built-in. And again, the current adblocker is too basic. I'm surprised they still haven't beefed things up. And uBlock Lite is pretty much a joke too.
-
@barbudo2005 said in How will Vivaldi deal with Google's Manifest V3?:
Explanation of “soon”:
1.- If you applied the register policy, “soon” means after June 2025.
2.- If you not applied the register policy, “soon” means between June 2024 and June 2025.
Yes, thanks for this info, this is indeed clear to me, I will certainly apply this registry tweak.
-
Feedbro:
Feeder is MV3, so Feedbro will do it:
"Changelog:
V8.0.0
This version is a complete rewrite to support new latest Manifest V3 platform."uBO:
Have you tried Adguard (MV3 Beta)?
Look this post and the following:
https://forum.vivaldi.net/topic/79579/manifest-v3-webrequest-and-ad-blockers/193
-
@DoctorG said in How will Vivaldi deal with Google's Manifest V3?:
WTF! Google!!1!11!! The worst thing Google tells me now and hitting on my hands to throw away needed work tools.
There are no Alternatives!Only Alternative would be Mozilla
BTW, how can you bring this info up again? I only saw it once when I upgraded to Viv 6.9, but then I made these warnings go away. But I forgot which of my extensions will soon not be supported anymore, at least not on the Chrome Web Store.
-
@RasheedHolland I had rebuild my broken 6.9 profile with a new one, and i never touched the OK again.
-
@barbudo2005 said in How will Vivaldi deal with Google's Manifest V3?:
Have you tried Adguard (MV3 Beta)?
Look this post and the following:
https://forum.vivaldi.net/topic/79579/manifest-v3-webrequest-and-ad-blockers/193
I agree with your post in the Adguard MV3 thread. Any adblocker should indeed have user rules management and element picker. But from what I understood, Adguard MV3 does offer this? Strange that Gorhill has not added these features in uBlock Lite yet.
