-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
No longer supported by chrome #616
Comments
Do you have a link about the current deprecation deadlines for Manifest 2? Firefox is still lagging behind for MV3 support, eg https://bugzilla.mozilla.org/show_bug.cgi?id=1685123 (see also w3c/webextensions#279). So I'm hesitant to move to MV3 since it would require to essentially maintain two versions. |
You can see the timeline here https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline |
Hi @tobiasdiez I'll clean it up a bit and upload a new branch with it, so it can be tested EDIT: I tested it just on Firefox at the moment.. |
I was a bit too optimistic. As far as I understand the service worker part is the big difference between firefox and chrome |
@LyzardKing Thanks for looking into this! Yes, the whole script evaluation construction may need to be changed. I think the first step would be to upgrade to the latest version of the zotero connector, see the end of https://github.com/JabRef/JabRef-Browser-Extension/blob/main/README.md#contributing-to-the-development. Most likely this already needs changes to the main code as well. Once this is done, we can try to use MV3, which is supported in the most recent version of the zotero connectors. |
Any hope of the exstension being updated so to be in line with the chrome requirements? For everyone utilising chrome it will be deactivated in the near future
The text was updated successfully, but these errors were encountered: