Permission warning for webRequest migration to declarativeNetRequest

[馮韋元]

Hello,

I'm seeing a behavior I didn't see previously in an earlier migration.

My MV2 extension is using webRequest + webRequestBlocking

My MV3 extension is using declarativeNetRequest (the mv3 equivalent)

When I test upgrade from MV2 to MV3 the extension gets disabled because of one apparently new permission: declarativeNetRequest

MV2 permission grant:

MV3 permission grant:

I don't see why the MV3 extension would require an additional permission when it is a forced transition from webRequest to declarativeNetRequest. That means we are forced to abandon all our users in order to complete this mandatory migration...

Any feedback or suggestions? Thanks in advance!!

[Juraj M.]

declarativeNetRequestWithHostAccess

[Mike-O]

I don't see the issue here,  馮韋元. Just add declarativeNetRequest and remove webRequestBlocking both in code and in your manifest. You can leave webRequest in your code and your manifest if you're only using chrome.webRequest for non-blocking tasks such as reading where people are visiting.

On your statement, "This means we are forced to abandon all our users in order to complete this mandatory migration," I don't see it as a forced abandonment. Your extension upgrades and those users come along with it.

[馮韋元 - Francois Devatine]

“The newest version of your extension has been disabled because it requires more permissions"

This is an issue :) But as other people pointed out, I should use declarativeNetRequestWithHostAccess which works fine for this update.