chrome v140+ now needs command line args when launching

  • --disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled

Building on our last workaround post https://hackertalks.com/post/13751580

and stealing from: https://superuser.com/questions/1917854/is-there-any-way-to-still-use-manifest-v2-extensions-in-google-chrome-139

no comments (yet)

sorted by: hot top controversial new old
there doesn't seem to be anything here