Manifest V3 support

[koryphaee]

For better or worse, Chrome is phasing out Manifest V2 in favor of V3.

My Chrome 127 is telling me this extension may soon™ be supported anymore:

Are there any plans to migrate to manifest V3?
Ideally no funcionality would be lost when doing so.
If that is not possible could a separate version (like uBlock Origin Lite) be the solution?

[extesy]

This is a non-trivial migration and I'm very short on time. Pull requests would be appreciated.

[extesy]

@GrosPoulet It looks like Chrome will soon kill the extension unless we migrate: https://www.androidpolice.com/chrome-canary-manifest-v2-extensions-ad-blockers-gone/

[Macleykun]

A few days ago the extension was removed for me thanks to the enforcement of manifest v3. My chrome version is 129.
For anyone who stumbles across this issue, to buy yourself more time until june 2025:

Scripted methode:

EnableManifestV2.reg.txt

1. Download the above txt file, inspect the content and then remove .txt part so the extension is .reg
2. Double click on this file to add the needed reg key.
3. Close all your chrome tabs
4. Visit https://chromewebstore.google.com/detail/hover-zoom+/pccckmaobkjjboncdfnnofkonhgpceea . You can now download and use hz+ again.

Manual methode:

1. In windows search go to: regedit
2. Then navigate to the following location: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies
3. You need to create a new folder named Google.
4. Within this new folder, create another folder named Chrome.
5. Within the Chrome folder, create a REG_DWORD key, with the name: ExtensionManifestV2Availability with an hex value of 2.
   
6. close all your chrome tabs.
7. Visit https://chromewebstore.google.com/detail/hover-zoom+/pccckmaobkjjboncdfnnofkonhgpceea . You can now download and use hz+ again.

[Eiion]

Just wondering if it would be considerably easier and less time consuming to previse a script version release (to be run in e.g. Tampermonkey) until a manifest v3 compliant extension release is available?
User scripts are what I'm currently switching to for important extensions that are already abandoned and will never make the switch to v3 or off those worked on until the switch is made.

Edit: Be very careful with and possibly reconsider using ExtensionManifestV2Availability as this might cause another issue you'd likely not want to deal with: https://support.google.com/chrome/thread/302850883/extensionmanifestv2availability-causing-your-browser-is-managed-by-your-organization?hl=en

[ZatsuneNoMokou]

@Eiion Or... Google being ennoying and to can get to publish a new version

[tetsuya-ops]

When is this going to happen?