Manifest v2 Sunset June 2025 and webRequestBlocking for Enterprise

[Cae Rule]

I am aware that June 2025 is the official sunset date for Manifest V2 in Chrome Enterprise according to https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline#june_2025_chrome_mv2_deprecation_enterprise_rollout

However, there is also this post (https://groups.google.com/a/chromium.org/g/chromium-extensions/c/CHWboTQ_rSM/m/Y1KVTxo3BgAJ) which contains this info:

"Are you planning to completely remove blocking webRequest APIs?

The observational capabilities of webRequest will remain in Manifest V3, but the introduction of declarativeNetRequest and planned changes to host permissions will significantly reduce the number of extensions that require the webRequest permission.

We are planning to disallow blocking webRequest in consumer extensions. Extensions that have been force-installed in managed environments via policies such as ExtensionInstallForcelist will be able to access blocking webRequest. If your extensions may be used in both and you opt to continue using blocking webRequest in managed environments, you will either need to distribute different versions for each environment or add conditional logic to gracefully handle when this feature is not available."

So I'm wondering, after June 2025, will an org using Chrome Enterprise, a self hosted extension, Manifest V3, and ExtensionInstallForcelist be able to continue using webRequest and webRequestBlocking?

Are there any plans from the Chromium team to officially sunset webRequest and webRequestBlocking in all use cases overall - and if so, is there a timeline on that?

Thanks so much. 

[Patrick Kettner]

Hi Cae,

Good question - as you mentioned in your quote, "We are planning to disallow blocking webRequest in consumer extensions. Extensions that have been force-installed in managed environments via policies such as ExtensionInstallForcelist will be able to access blocking webRequest". As a result, we do not have any plans as of now to officially sunset webRequest and webRequestBlocking in all use cases overall.

--
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/1f510118-d82d-4e2e-91a2-25644f54f3den%40chromium.org.

[Cae Rule]

Hi Patrick,

Thanks so much for your response. I appreciate the clarity, especially because the quoted post is from five years ago and things can change a lot in that amount of time. Good to hear!

Cheers,

C

[Patrick Kettner]

Absolutely! I think my team certainly hasn’t done a perfect job with communicating a lot of things so I absolutely understand the hesitation

Cheers

[Mike-O]

So, is Google going to begin to block chrome.webRequest.* APIs for consumer extensions? If so, when? Will all the APIs for chrome.webRequest be blocked or only some of them? Currently my MV3 extension is using chrome.webRequest.onCompleted and chrome.webRequest.onBeforeRedirect.

[Patrick Kettner]

Nothing is changing.

Anything that is unsupported was removed for manifest V3 was done for years at this point, and will continue to not be supported.

The pieces that you mentioned are supported a manifest v3, and will continue to be supported to manifest v3.