In Manifest v3

[Hames0024]

Your code is impossible in v3.
Right?

[ethanjerrum5]

@Hames0024 - This is something I'd like to know also, any update here please?

[markrosenbaum]

Unfortunately due to the Manifest V3 changes I don't believe the functionalities previously held by this extension are possible anymore. According to Google "Manifest V3 changes how extensions handle modification of network requests. Instead of intercepting network requests and altering them at runtime with chrome.webRequest, your extension specifies rules that describe actions to perform when a given set of conditions is met. Do this using the Declarative Net Request API."

[ethanjerrum5]

Thank you for the update @markrosenbaum

[frederik-uni]

reenable v2
Mac:

defaults write com.google.Chrome ExtensionManifestV2Availability -int 2

Windows:

regedit `Software\Policies\Google\Chrome\ExtensionManifestV2Availability` to 2

[stephenkall]

reenable v2 Mac:

defaults write com.google.Chrome ExtensionManifestV2Availability -int 2

Windows:

regedit `Software\Policies\Google\Chrome\ExtensionManifestV2Availability` to 2

Just a reminder that this will work up until June/25. After that, we're probably gonna have to move to a different solution.

[digifomation]

chrome://flags/

there a news option!

Allow legacy extension manifest versions
Allows extensions with legacy (unsupported) manifest versions to be loaded as unpacked extensions. This should only be used for maintaining legacy extensions and will be removed in the future. – Mac, Windows, Linux, ChromeOS

#allow-legacy-mv2-extensions

[harishletsgo]

@Hames0024 I rewrote the v2 version for v3 and published it on the Chrome Web Store -> https://chromewebstore.google.com/detail/tamper-dev/cpcmdnpekbomkhllkbmghhbefjbbjgni

[markrosenbaum]

Hi @harishletsgo, is there any chance you'd be willing to publish the new source to GitHub just for continuity?