-
-
Notifications
You must be signed in to change notification settings - Fork 151
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
Chrome extension "no longer supported" #1674
Comments
Hi, thanks for the report. This is indeed caused by the need to migrate to Manifest V3 ( #1193 ). Unfortunately I have very little time to work on Firenvim these days, so I doubt I'll manage to do it anytime soon :(. |
This deals a legitimate and significant blow to my motivation to continue learning to code, as I used it to replace the crappy "vim" mode in web editors on sites teaching coding. I hope this magical extension is revived soon. Thank you for everything @glacambre. |
@Crackerfracks Consider using a different web browser. It isn't just Firenvim affected, other good extensions are affected too and the reason is Google is removing APIs that don't fit their agenda. A case study is |
@alerque It's kind of a hard sell when 60%+ of the world uses Google Chrome and only 6-7% Firefox and Edge combined. Shame about the policy change though. And I fear that if glacambre doesn't have the time to make the required updates, then nobody else will have the motivation either. |
Not anymore after today's update :( |
very sad news :( |
Chrome recently changed their security guidelines or something and we got this:
The extension still works (I used it to create this issue), but maybe there's something that should change in order to keep up to date securitywise. I think it has to do with this.
The text was updated successfully, but these errors were encountered: