Manifest V2 to V3 updating

[A]

Given the massive issues with checking manifest v3 extensions, I am concerned about disabling my manifest v2 extension before the check is complete. This will have catastrophic consequences that will destroy the project.

I believe that the manifest v2 disabling phases should have happened in the following order:
- disabling the creation of new manifest v2 projects
- disabling the ability to update manifest v2 projects (only to mv3)
- announce a specific date by which you need to upload an update to the project from mv2 to mv3
- wait for all uploaded manifest v3 projects to be checked by moderators
- begin a gradual disabling of manifest v2

This sequence would be clearer and more convenient for all developers. Given all the inconveniences and errors of manifest v3, as well as the lack of specifics about the transition dates, this creates big problems and risks for developers. In addition, a fairly large number of users are still using outdated Chrome browsers version 109 and below, which do not support many important mv3 fixes.

I hope the Chrome extensions team will not make any radical and sudden decisions that will harm developers.

Thank you.

[Patrick Kettner]

Which issue are you referring to?

--
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 visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/bcd7bf58-2d45-429a-aab9-4de15e2b5e34n%40chromium.org.