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
You must log in or register to comment.
