In the future, does manifest v2 will be remove and force all extension update to manifest v3

464 views
Skip to first unread message

Ngoc Duc Huynh

unread,
Jun 30, 2021, 12:06:51 PM6/30/21
to Chromium Extensions
As far as I know, manifest v3 have service worker which replace background script, but I hear it still have limit:
- However, there may be differences due to the inferior nature of service workers as this is still an immature Web technology so it doesn't support things we grew accustomed to such as dynamic script loading, ES modules, clipboard handling, DOM parsing, and a lot more.
In the future we will be force update to v3? If so, this may sound not good for me

Shu

unread,
Jun 30, 2021, 12:12:17 PM6/30/21
to Chromium Extensions, provan...@gmail.com
MV3 has a lot of limitations, and as I understood we will be forced to update to v3 one day. There was written somewhere, that MV2 support will be stopped but it will be announced at least 1 year in advance... So, we have at least 1 year, I guess and I hope mv3 will be improved meanwhile

Simeon Vincent

unread,
Jun 30, 2021, 9:17:07 PM6/30/21
to Shu, Chromium Extensions, provan...@gmail.com
In the future we will be force update to v3? If so, this may sound not good for me

It depends on what you mean by "force." At some point in the future the Chrome Web Store will no longer accept Manifest V2 extensions. At some point after that Chrome will stop loading Manifest V2 extensions. As such, if an extension is not migrated to Manifest V3 it will eventually cease to function. Ultimately, though, it's a developer's choice on whether or not they want to update their extensions.

Ngoc, I don't know where the quotation you provided came from, but I have two quick clarifications. First Manifest V3 does not allow "dynamic script loading", but this change is not related to service workers. Even if Manifest V3 supported background pages, we still would not allow extensions to execute remotely loaded code. Second, support for extension service worker modules landed in Chrome 91. It is now possible to use static import in extension service workers. (Dynamic import is still disallowed by the HTML spec.)

Service workers have other functionality gaps and Chrome's extensions team is actively exploring ways to address them. 

Simeon - @dotproto
Chrome Extensions DevRel


--
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/aa802cb8-3a63-498a-95c8-5c2567bcd06en%40chromium.org.

Ngoc Duc Huynh

unread,
Jun 30, 2021, 9:54:09 PM6/30/21
to Chromium Extensions, Simeon Vincent, Chromium Extensions, Ngoc Duc Huynh, Shu
Thank you for your response, maybe it too soon for me to conclude the v3, will hope it improve in future

Vào lúc 09:17:07 UTC+8 ngày Thứ Năm, 1 tháng 7, 2021, Simeon Vincent đã viết:
Message has been deleted

John

unread,
Jul 2, 2021, 9:22:21 AM7/2/21
to Chromium Extensions, Simeon Vincent, Chromium Extensions, provan...@gmail.com, Shu
Simeon,

Would this mean that users with a manifest v2 extension would eventually have that extension disabled if not updated to manifest v3? Also, what if an extension in question was taken down? Would those users be lost since we don't necessarily have the option to update them? Thank you for the clarifications!

Cuyler Stuwe

unread,
Jul 13, 2021, 7:57:49 PM7/13/21
to Chromium Extensions, John, Simeon Vincent, Chromium Extensions, provan...@gmail.com, Shu
For all intents and purposes, the TL;DR of Simeon's answer is:

"Yes."
Reply all
Reply to author
Forward
0 new messages