extesy
Manifest V3 support
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?
This is a non-trivial migration and I'm very short on time. Pull requests would be appreciated.
@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/
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:
- Download the above txt file, inspect the content and then remove .txt part so the extension is .reg
- Double click on this file to add the needed reg key.
- Close all your chrome tabs
- Visit https://chromewebstore.google.com/detail/hover-zoom+/pccckmaobkjjboncdfnnofkonhgpceea . You can now download and use hz+ again.
Manual methode:
- In windows search go to: regedit
- Then navigate to the following location: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies
- You need to create a new folder named Google.
- Within this new folder, create another folder named Chrome.
- Within the Chrome folder, create a REG_DWORD key, with the name: ExtensionManifestV2Availability with an hex value of 2.
- close all your chrome tabs.
- Visit https://chromewebstore.google.com/detail/hover-zoom+/pccckmaobkjjboncdfnnofkonhgpceea . You can now download and use hz+ again.
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
@Eiion Or... Google being ennoying and to can get to publish a new version
For me it was last week. Just re-activate it. It will work until v2 support gets completely removed from chromium based browsers. Still, it's time to look for an alternative or to update Hoverzoom. .
Thanks to all the work that was merged in: https://github.com/extesy/hoverzoom/pull/1522 The version over at: https://chromewebstore.google.com/detail/hover-zoom+/pccckmaobkjjboncdfnnofkonhgpceea
Is now manifest V3 compliant! ✨ so far it works perfect! The version there is 1.0.229, because of the following reason:
Sounds good. I'm going to merge this branch and publish a new build but only for Chrome because it got disabled there. After that I'll wait for some time in case there are any serious bugs found, and if not then I'll publish it for Firefox and Edge. Thank you for testing!
https://github.com/extesy/hoverzoom/pull/1522#issuecomment-2722798079
Thank you guys for your continued efforts to keep the extension alive and working!
With the newest Version 1.1.0 I've just ran into an error with the Extension on Brave Browser (so far no reaction to the update in Chrome):
Given the previous version 1.0.229 ran without issues or warnings on Brave, I wonder what change from 1.0.229 to 1.1.0 is causing that.
Brave is up to date - Version 1.76.81 Chromium: 134.0.6998.166 (Official Build) (64-bit)](https://brave.com/latest/)
@Eiion please see my response in https://github.com/extesy/hoverzoom/issues/1584#issuecomment-2745340545
So hover zoom + will not snoop into my history right? Its just for MV3?
@anirudhp06 yes, that's correct