JabRef / JabRef/JabRef-Browser-Extension
Extension still partially broken on Firefox
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 96
- Forks
- 28
- Avg merge
- 2h 50m
- Merged PRs (30d)
- 14
Description
Hi all,
This is in reference to #638. First of all, thanks for responding to my original ticket. I have just checked if the problem was solved with the newer version of the extension (I'm running 3.2.2 updated on May 4, 2026). What is happening is that importing from the browser has resumed to work but only when there is no Jabref instance running: in that case the behavior I see is that on click on the extension a new instance of Jabref is started, and then the import dialog appears on Jabref. If instead there is already a Jabref instance running, nothing happens. I am attaching the logs from Firefox's browser console, using the same ArXiv link as in the original ticket (https://arxiv.org/abs/2603.22277).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing #638 and the attached Firefox browser-console log, then reproduce the ArXiv import with JabRef already running and with no instance running. Trace the browser-extension-to-JabRef launch and import path; done means clicking the extension imports successfully into an existing JabRef instance without requiring a new one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100