After adding multiple files some of them are not visible in the "General" tab

[mpatas]

JabRef version

5.10 (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

1. Add a bibliographic record.
2. Go to "General" tab in entry editor.
3. Add a linked file.
4. Try to scroll the "File" field down and up.
5. Repeat steps 3 and 4 several times (adding four files seems to trigger the bug).

When first three files are added, they are visible in "File" field. Scrolling is not necessary with three files, so scroll bar is not visible. All is fine. When the fourth file is added, the scroll bar appears, but the fourth file itself is not visible. Furthermore, scrolling seems to work "jittery" (it still fails to find that fourth file)... Yet, if we go to to "BibTeX source" tab, all four files are mentioned in the record, so, the fourth one is only missing from that element of UI.

When the fifth file is added, the fourth one seems to reappear, with scrolling working in still more unpredictable ways...

Appendix

No response

[AEgit]

Note, that this issue is (indirectly) connected to the following issue:
#8823
and has been noted even earlier on: #5105 (comment)

You should be able to see more than 3 linked files in the editor view, without having to scroll.

[mpatas]

You should be able to see more than 3 linked files in the editor view, without having to scroll.

I wonder if that will solve this problem, or will it increase the threshold when the bug happens? (Not the same as solving it, but still a bit of an improvement.)

[AEgit]

It might just increase the threshold (more likely) thus providing a workaround to a certain extent (and solving the older bug reports indicated) or the indicated issues are directly related and solving the older issues also automatically solves the issue reported here.