Skip to content
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

This extension may soon no longer be supported because it doesn't follow best practices for Chrome extensions. #353

Open
michaelkrieger opened this issue Jul 30, 2024 · 3 comments

Comments

@michaelkrieger
Copy link

Chrome says "This extension may soon no longer be supported because it doesn't follow best practices for Chrome extensions. (Learn more)"

Needs an update soon, I would assume?

@bogenpirat
Copy link
Owner

i guess there's still the option to manually re-enable it then... but yeah, this has been coming for quite some time and i guess i should tend to migrating it to v3 at some point. last i checked, this is not a trivial task, so it'll take some resources. i'll update this issue once i'm done

@SiriosDev
Copy link

news?

@Elegant996
Copy link

Elegant996 commented Sep 16, 2024

You could also assist with migrating instead of asking for an update. There are tons of browsers (other than Chrome!) that support manifest v2. I tried to do the migration myself on a fork but it's much more daunting than you'd expect. They really do not want us loading multiple scripts simultaneously. This may mean the addon needs to become more modular.

This would take more time and could require a re-write of several areas unless v3 becomes more lax.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants