tamperchrome In Manifest v3

Your code is impossible in v3. Right?

Nov 16 '22 23:11 Hames0024

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

Aug 23 '24 12:08 ethanjerrum5

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."

Nov 12 '24 14:11 markrosenbaum

Thank you for the update @markrosenbaum

Nov 12 '24 14:11 ethanjerrum5

reenable v2 Mac:

defaults write com.google.Chrome ExtensionManifestV2Availability -int 2

Windows:

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

Dec 04 '24 10:12 frederik-uni

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.

Jan 08 '25 21:01 stephenkall

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

Jul 11 '25 17:07 digifomation