MV3 extension testing

[Tom Riley]

I'm working on a refactor of an MV2 extension to MV3.

I need to use the new "declarativeNetRequestWithHostAccess" and "webRequestAuthProvider" but it's not clear if "webRequest.onCompleted" and "webRequest.onErrorOcurred" will still be available?

Is there a version of Chrome/Chrome Canary, or a way to test, that will enforce all of the MV3 changes as they will be required by the Chrome web store when it deprecates MV2? Or, is it a case of submitting the new "working" MV3 extension as a draft, and exposing that to some internal test users? In this case, would the Chrome web store not accept the extension if it is not sufficiently transitioned to MV3?

Thanks to anyone who can help.

[Oliver Dunk]

Hi Tom,

There aren't any breaking changes planned between now and the MV2 deprecation. Anything the browser will enforce is already enforced - the only thing not caught by this is anything which would be a violation of Chrome Web Store policy.

webRequest.onCompleted and webRequest.onErrorOcurred will still be available but not with the "blocking" option. That means you can observe requests if you have host permissions but cannot make blocking changes to them.

Let us know if you have any more questions!

Thanks,

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

--
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/bff2b1b4-851a-429f-809b-bb243d84cac6n%40chromium.org.

[Tom Riley]

(re-posting this comment, last time got deleted, sorry if I did something wrong)

Thanks Oliver.

I presume there will be some warning procedure before the deprecation date if an MV3 extension is not "valid" somehow? I mean in the scenario that we get everything working how we want and successfully update the MV2 extension -> MV3 version in the web store, and test the update process for users, can we then be confident we've done everything we need to not be affected by the MV2 deprecation?

[Oliver Dunk]

(re-posting this comment, last time got deleted, sorry if I did something wrong)

You're all good! Apologies for this, it is a bug which comes up infrequently but not never in the mailing list.

in the scenario that we get everything working how we want and successfully update the MV2 extension -> MV3 version in the web store, and test the update process for users, can we then be confident we've done everything we need to not be affected by the MV2 deprecation?

In most cases, yes. There's a little bit of nuance - for example, if your extension is used in enterprise it's possible an admin has pinned an older version of the extension. For end users that are receiving automatic updates, though, you should be good.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB