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

No longer supported by chrome #616

Open
egen97 opened this issue Jan 20, 2025 · 5 comments
Open

No longer supported by chrome #616

egen97 opened this issue Jan 20, 2025 · 5 comments

Comments

@egen97
Copy link

egen97 commented Jan 20, 2025

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

@tobiasdiez
Copy link
Member

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.

@egen97
Copy link
Author

egen97 commented Jan 21, 2025

You can see the timeline here https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline
It has been deprecated for consumers already, so new users cannot download the extinction, even though users who already has it installed may continue to use. The exact time they will loose access does not seem to be specified, other than before summer.

@LyzardKing
Copy link
Collaborator

LyzardKing commented Jan 21, 2025

Hi @tobiasdiez
I wrote up a very basic version that seems to work.
The main thing we need to change is that extensions cannot access remote data (such as the tailwind css stuff).

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..

@LyzardKing
Copy link
Collaborator

I was a bit too optimistic.
The actual big issue is that on chrome we need just one background script, that acts as the service worker.
This would require changing how the zotero connector files are loaded (plus some minor changes that are valid in firefox as well).

As far as I understand the service worker part is the big difference between firefox and chrome

@tobiasdiez
Copy link
Member

@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.

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

3 participants