Migrate to manifest v3

[jeremybergen]

Google is requiring all extensions to be running manifest v3 starting in June 2024. This extension is currently on v2 and thus will need to be migrated. I have looked into the requirements for migrating and it looks like there will need to be significant rewrites to conform to v3.

A big change that affects this extension is the background scripts. In v2, you can list several scripts that are loaded in the background however in v3, you can only have a service_worker script. That script can load other scripts however the issue is that there is no DOM or local storage for the service_worker script. This breaks jquery and fancy-settings. I believe that fancy-settings can get replaced with localForage but I haven't dug into it that much.

So the extension is unable to be migrated to v3 without changing quite a bit of behavior and I believe a significant rewrite on how it is currently working. I am not a javascript developer and I do not know if I have enough time to devote to learning and rewriting this extension however I do not want to see a useful extension disappear. I'll keep working on it in my spare time however if anyone is more experienced in extension development/javascript, I would much rather pass it onto them.

This issue can be used to track current migration status.

[gboudreau]

Quick tip: you can get a few months of v2 extension by using this flag: chrome://flags/#extension-manifest-v2-deprecation-disabled
Change it to Disabled and restart Chrome. Extensions using manifest v2 will continue to work (until Google removes this flag).