You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Latest development branch build (please note build date below)
Operating system
MacOS
Details on version and operating system
MacOS Sequoia 15.0
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
Do a fulltext search in a library
Switch to another db/library
Switch back to the first library and check the search results tab
Turning off and on the fulltext flag again will make the results appear correctly.
Doing a sort of "hack" where we reset the flag (if it is active) every-time a library is switched seems to prevent the issue, like this : stateManager.activeDatabaseProperty().addListener((_, _, _) -> { if (preferences.getSearchPreferences().isFulltext()) { Platform.runLater(this::resetFulltextFlag); } else { content.getChildren().clear(); } });
But it's just an hack and also seems to create problems with threads concurrency (I can post a video of this behavior as well if needed).
JabRef version
Latest development branch build (please note build date below)
Operating system
MacOS
Details on version and operating system
MacOS Sequoia 15.0
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
Turning off and on the fulltext flag again will make the results appear correctly.
Doing a sort of "hack" where we reset the flag (if it is active) every-time a library is switched seems to prevent the issue, like this :
stateManager.activeDatabaseProperty().addListener((_, _, _) -> { if (preferences.getSearchPreferences().isFulltext()) { Platform.runLater(this::resetFulltextFlag); } else { content.getChildren().clear(); } });But it's just an hack and also seems to create problems with threads concurrency (I can post a video of this behavior as well if needed).
Appendix
Screen.Recording.2025-06-02.at.23.19.03.mov
No errors in the log.