Jump to content

Resuming the transition to Manifest V3


Sampei.Nihira

Recommended Posts

Posted (edited)

Today I checked how many extensions I have installed in Edge (4) already use MV3.

  • uBlock Origin Lite - MV3
  • SwiftDial - MV3
  • Video DownloadHelper - MV3 - off by default
  • Stream Recorder - MV3 - off by default

With Firefox (3):

  • uBlock Origin - MV2
  • HLS Downloader - MV2 - off by default
  • Video DownloadHelper - MV2 - off by default
Edited by Sampei.Nihira
Link to comment
Share on other sites


On 5/31/2024 at 2:29 PM, Sampei.Nihira said:

This will be the notice of disabling MV2 extensions:

 

1.jpg

The warning is there for ages. If you go to "manage extensions", click any extension and under "errors" you will see.

Link to comment
Share on other sites

15 hours ago, Sampei.Nihira said:

Today I checked how many extensions I have installed in Edge (4) already use MV3.

  • uBlock Origin - MV2
  • Video DownloadHelper - MV3
  • Stream Recorder - MV3
  • SwiftDial - MV3

 

Good for you! For me ... well, it kinda sucks, almost all extensions I used were free, but now are paid with the Manifest V3.

Link to comment
Share on other sites

The only question here is whether MSFN members are able to verify whether their extensions are already at MV3 or are always at MV2.
Those who can verify it as I did,the better for them.

The switch that will allow a disabled MV2 extension to be rehabilitated will be short-lived.
If an MV3 extension is not chosen that will be offered as a replacement.

Of course I personally do not care about all of the above.

 

Link to comment
Share on other sites

Mileage will vary.

But I have had some MV2 extensions migrate to MV3 and have EASILY downgraded back to MV2 just by overwriting my local MV2 with files from the newer MV3 and keeping the MV2 manifest format.

But you do have to have your MV2 archived locally.

MV2 or MV3, I myself *never* install directly from the Chrome Web Store.

Link to comment
Share on other sites

Posted (edited)

Hmmmmm........

MV2 extensions were allowed to create background pages. These pages allow running JavaScript code and keep state like variables for the whole browser session.
Migration to stateless or non-persistent background pages is needed for MV3.

Not counting service workers.

The operation of an MV2 extension differs from an MV3 extension.

 

P.S.

 

However, switching or modifying (I understand although in my opinion it will be unnecessary) extensions from MV2 to MV3 is not the purpose of this thread.

Edited by Sampei.Nihira
Link to comment
Share on other sites

Posted (edited)

Chrome 127 stable will be released on July 23.

Before this date I would like to advise all MSFN members to check for MV2 extensions installed in their Chromium-based browsers.
That they should (if they want to survive) shortly upgrade to MV3.

It is possible to carry out this control by 2 methods,the simplest one shown in the image below:

FMt3r4W.jpeg

All your extensions installed with Inspect views identical to the red arrow will be MV2.
Extensions showing Inspect views like the blue arrow will be MV3.

Those who want to follow a more "complicated" method can see the above using:

chrome://extensions-internals

MSFN members who want to check extensions in Firefox (but obviously this is less important) can use the debug extensions:

ntAXJQi.jpeg

 

Extensions installed with the blocked background script highlighted by the blue arrows will be MV3.

The others highlighted by the red arrow MV2:

wOgtEtw.jpeg

 

Edited by Sampei.Nihira
Link to comment
Share on other sites

I'll cancel the internet subscription before they get me to use Chrome 127. I've gotten rid of both Supermium and Thorium, still too many Google's fingerprints all over the place, think I'll just use Firefox as a backup until that browser is ruined completely too.

Link to comment
Share on other sites

Posted (edited)

In the opinion of some of my former colleagues.....not too long.
MV2 extensions would be disabled anyway.
As is the case for any dangerous extensions.

Of course, this is all to be proven.:rolleyes:

Edited by Sampei.Nihira
Link to comment
Share on other sites

Posted (edited)

Nothing will change.

MV2 extensions that will not transition by choice of their developers to MV3,such as uBlock Origin  will be abandoned after June 2025.

Indeed, it is likely that in this transition year the development of uBlock Origin for Chromium-based browsers will slow down compared to the same version for Firefox-based browsers.

On the other hand more and more users will install in their Chromium-based browsers uBlock Origin Lite,AdGuard extension MV3........etc.....and thus this state of abandonment will be accelerated by several parties

Although I have the company policy already installed,personally if there is a slowdown in the development of uBlock Origin for Chromium based browsers,such that the functionality of the extension is reduced compared to the same version for Firefox I will switch to another MV3 adblocker without delay.
Probably adGuard extension whose development I have been following for at least 6 months.
I am just waiting for the problems that I have also opened to be solved.

And of course that the current stable version be merged with the experimental MV3 version.
 

If the future events hypothesized above come true.:dubbio:

Edited by Sampei.Nihira
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...