-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manifest v3 breaks v4.3.6 #421
Comments
Ouch, I don't even know how that happened. |
I just went for a small nap, and everything went to hell 😆, this is the biggest release ever lol. |
Both on dev (local) and stable (store) versions (Google Chrome):
But it does not seem to stop the extension. |
It's almost unbelievable how many people you have awakened by breaking the addon for a day, the forums, discord, store reviews... :D |
:D :D |
Ahhhh.... the GIF-Fu is strong with this one. |
@GramThanos if I select this: I see this: there used to be numbers, no? Is it bugged? Can you check it please? |
Ahhh, I see, I forgot we have a documentation, I was never using this (using the % option) and I thought it bugged, nevermind, sorry to bother you @GramThanos :D |
Only the color changes with that option |
In it's current state, you can't load the dev version from a folder in Firefox? I've tried manifest.json and manifest_v2.json and both are throwing the same error.
It's not about me tho, I just want to prevent any future extension problems, I am not watching it closely, but it is very likely, that Thanos does some changes so it works on Firefox. |
Ah, I see, I always get the idea AFTER I ask here, I renamed the manifest_v2 to manifest and it works. I only got:
But I suppose that's nothing important. |
The manifest v3 broke the addon. The current version on chrome store don't runs at all.
I am working on a fix.
The text was updated successfully, but these errors were encountered: