What is the exact date of Enforcement of MV3 on Chrome browsers? Currently it is mentioned as early as June 2024, but it doesn't mention any date - https://developer.chrome.com/blog/resuming-the-transition-to-mv3
What will happen if our extension remains as MV2 in June 2024 also, since enforcement is only on pre-stable versions of Chrome (Dev, Canary, and Beta), will it impact other Chrome users OR will our extension be blocked on Chrome Store itself during the pre-stable phase also?
--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/bf603a30-bc0d-4246-a314-de3d9b5b61b5n%40chromium.org.
Thanks Oliver for the update. The I/O talk was helpful to know about the latest updates.
One more clarification, just to be sure nothing changed based on the announcement in the I/O talk.Would MV3 extensions shared outside of Chrome Store, with Remote Code Execution logic, be allowed on Chrome Browser after June 2024 enforcement of MV3 to get sideloaded in the below 2 cases :
- Installing extension via Load Unpacked (ZIP) with Developer Mode = ON
- Installed forcefully with a group organisation's IT team (ExtensionManifestv2Availability is NOT enabled) and Developer Mode = OFF
My understanding is that - warnings and eventual blocking of extensions is applicable only to MV2 extensions and not for MV3 extensions like above. Kindly clarify.
Thanks,
Sarthak
Given that, will updates to MV2 extensions still be possible before v127 moves to stable?
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/CAOsQqBnp%3DqvWwYQMwG0Ftn-OB0%2BZTaauQDCNEdjadovnV6F_Sg%40mail.gmail.com.
Oliver, can you clarify on the discrepancy between your comment and woxxom's comment? (I also notice there is a comment from Patrick Kettner in a separate conversation that implies that changes are limited to Chrome 127 and above
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/CA%2BjwbLzre2QsJf%2B2cwqxMCowPs6J9sXmzQP8Xkt-WHbDmAGnzg%40mail.gmail.com.
If users continue to use a browser version lower than 127, will MV2 extensions continue to work normally (not be disabled)?
User with Chrome 126 with extension not updated to MV3. What will happen once they updated? Will Chrome update the extension automatically for them o do they have to go to Chrome Store and manually perform any actions there?
We would also like to know about what will happen with MV2 support in 127. Will be still available?
Hello Oliver,
Thank you very much for your reply; it has cleared up the confusion I had about MV2. I would like to discuss a problem I am currently facing and seek your advice on how to resolve it or any other possible solutions.
As I mentioned in my previous question, My company has many users who are still on Windows 7, and Chrome will no longer update for them. They can only continue to use the MV2 extension. However, my company's MV2 extensionhas been marked as malicious by Chrome (plugin ID: nhkjnlcggomjhckdeamipedlomphkepc), and we only recently became aware of this issue. All of our Windows 7 customers are unable to use our product (my company, www.yingdao.com, is an RPA company from China, similar to UiPath, providing browser automation capabilities). Is there any way I can make our MV2 plugin usable again? I look forward to your response!