When opening JabRef, Ctrl+W does not behave as expected.

[priyanshu16095]

JabRef version

5.15 (latest release)

Operating system

Windows

Details on version and operating system

No response

Checked with the latest development build (copy version output from About dialog)

• I made a backup of my libraries before testing the latest development version.
• I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

There is a bug in the Ctrl+W shortcut. Instead of closing the current tab, it always closes the first tab in JabRef.

1. Open JabRef.
2. Use Ctrl+W key.
3. It will close the first tab, instead of current tab.

Recording.2025-02-19.mp4

[urlyy]

On my Ubuntu 24.04, I've observed this effect as well. I've traced it to the CloseDatabaseAction class in the file java/org/jabref/gui/frame/JabRefFrame.java, where the logic for close current library is implemented.

However, when running the program, it seems to only close the libraryTab member variable ( Only execute the code within the green box in the following figure ). However, libraryTab is always the first tab, not the current tab. And after closing, it does not update libraryTab. This results in the next use of Ctrl+W not being able to close the newest first tab, effectively doing nothing.

I have currently only located the position where the error occurs, and I haven't delved into it deeply yet. I haven't understood the significance of libraryTab at the moment.

I think we need to change it to use only tabContainer.getCurrentLibraryTab().

[urlyy]

/assign-me

[github-actions]

👋 Hey @urlyy, thank you for your interest in this issue! 🎉

We're excited to have you on board. Start by exploring our Contributing guidelines, and don't forget to check out our workspace setup guidelines to get started smoothly.

In case you encounter failing tests during development, please check our developer FAQs!

Having any questions or issues? Feel free to ask here on GitHub. Need help setting up your local workspace? Join the conversation on JabRef's Gitter chat. And don't hesitate to open a (draft) pull request early on to show the direction it is heading towards. This way, you will receive valuable feedback.

Happy coding! 🚀

⏳ Please note, you will be automatically unassigned if the issue isn't closed within 90 days (by 23 May 2025). A maintainer can also add the "📌 Pinned"" label to prevent automatic unassignment.

[urlyy]

I apologize. I would like to unassign myself from this issue.Due to various reasons that have kept me quite busy, I won't be able to continue working on this issue. Just allowing others to contribute and solve this issue as soon as possible.

[urlyy]

/unassign-me

[github-actions]

👋 Hey @urlyy, you've been automatically unassigned from this issue due to inactivity.

Note

If you'd like to be re-assigned, just leave another comment or ask a maintainer to assign you again.
If you're still actively working on the issue, let us know by commenting, and we can pin it to prevent automatic unassignment.

[AashifAmeer]

/assign-me

[github-actions]

👋 Hey @AashifAmeer, thank you for your interest in this issue! 🎉

We're excited to have you on board. Start by exploring our Contributing guidelines, and don't forget to check out our workspace setup guidelines to get started smoothly.

In case you encounter failing tests during development, please check our developer FAQs!

Having any questions or issues? Feel free to ask here on GitHub. Need help setting up your local workspace? Join the conversation on JabRef's Gitter chat. And don't hesitate to open a (draft) pull request early on to show the direction it is heading towards. This way, you will receive valuable feedback.

Happy coding! 🚀

⏳ Please note, you will be automatically unassigned if the issue isn't closed within 45 days (by 22 April 2025). A maintainer can also add the "📌 Pinned"" label to prevent automatic unassignment.