JabRef 5.0-dev
Windows 10 10.0 amd64
Java 11.0.3-bellsoft
The ViewModelCellListFactory produces strange behaviour in combination with comboBoxes. In long lists the hover-indicator is displaced in relation to how far the list can be scrolled down.
Appears only with comboBoxes, other lists seem to work well.
Despite this bug, selection works.
Bug was mentioned in the PRs #5185 and #5265
Steps to reproduce the behavior:

JabRef 5.0-dev
Linux 5.0.0-27-generic amd64
Java 1.8.0_222
Cannot reproduce the behaviour mentioned above. I reckon this has now been fixed with https://github.com/JabRef/jabref/pull/5265 (?).
I will start investigations on this
JabRef 5.0-dev
Linux 5.0.0-27-generic amd64
Java 11.0.4
Ok, I can now reproduce this behaviour with the current snap version on the --edge channel. This indicates that this issue was introduced somewhere between the release of the current snap version (or rather the one from 9th September) on the --beta channel and the current snap version on the --edge channel.
@CyraxSector You can try to narrow down the bug a git bisect:
https://git-scm.com/book/en/v2/Git-Tools-Debugging-with-Git
Cannot reproduce the behavior mentioned above. Can you please provide more information.
JabRef 5.0-dev--snapshot--2019-09-26--master--1a6c92c79
Windows 10 10.0 amd64
Java 11.0.4-bellsoft
I can still reproduce this behaviour. You can force it to happen by scrolling with the mouse wheel in the fetcher sidepane and then switching back to just scrolling with the mouse.
If you just scroll with the mouse (without using the mouse wheel) you will sometimes encounter the issue and sometimes not. But by using the mouse wheel scrolling first and then the mouse scrolling itself afterwards, the issue always appears.
This should be fixed in the latest development version. Could you please check the build from http://builds.jabref.org/master/. Thanks! Please remember to make a backup of your library before trying-out this version.
JabRef 5.0.0-dev--2019-10-18----bc26c3ac5
Windows 10 10.0 amd64
Java 12.0.2
I can confirm that this has been fixed in the current dev version.