Migrate to manifest v3

[jamesmortensen]

Thank you for making this extension. It's one of my favorites, and I've been using it for many years.

Google is soon going to pull support for manifest v2 extensions in 2023. In January 2023, the only updates the Chrome Web Store will accept is for migrating extensions to manifest v3.

My suggestion would be to first experiment with injecting and running JavaScript on pages, since this is core to the extension's functionality and since this JavaScript is user-supplied and not part of content scripts or extension files. Manifest v3 does a lot to restrict what extensions can do with JavaScript that is not part of the actual extension. If this works without issues, then I think the rest of the work would be relatively straightforward, such as converting the non-persistent background page to a service worker and adjust manifest permissions to the new platform.

https://developer.chrome.com/docs/extensions/mv3/intro/mv3-migration/

[CypherVault]

Thank you for making this extension. It's one of my favorites, and I've been using it for many years.

Google is soon going to pull support for manifest v2 extensions in 2023. In January 2023, the only updates the Chrome Web Store will accept is for migrating extensions to manifest v3.

My suggestion would be to first experiment with injecting and running JavaScript on pages, since this is core to the extension's functionality and since this JavaScript is user-supplied and not part of content scripts or extension files. Manifest v3 does a lot to restrict what extensions can do with JavaScript that is not part of the actual extension. If this works without issues, then I think the rest of the work would be relatively straightforward, such as converting the non-persistent background page to a service worker and adjust manifest permissions to the new platform.

https://developer.chrome.com/docs/extensions/mv3/intro/mv3-migration/

Seconded. Would just that really update this for manifest v3?

[jamesmortensen]

@CypherVault The biggest question mark is the restriction on executing arbitrary JavaScript that is not part of the extension. Since that is the purpose, if we can't do that anymore, then nothing else matters.

You can read more about the "scripting" permission here: https://developer.chrome.com/blog/crx-scripting-api/

It looks to me like it might not be possible, but I hope someone else can read this and possibly see something I missed. Extensions like this are awesome.