Search Focus switches to author field - possible bug

I use jabreb about once a minute while working with about 6000 entries. On the 5.0 alpha version I have to following issue that is quite annoying.

After a search the cursor is blinking in the SEARCH field. Now if I backspace, it deletes the AUTHOR field in the currently open entry. I have deleted dozens of author entries because of this....

Even though the cursor is in the search field, I have to make sure I double click to avoid killing the author field. This does not occur on jabref 4. Hopefully we can fix this?

Is your suggestion for improvement related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Additional context
Add any other context or screenshots about the feature request here.

[tobiasdiez]

Duplicate of #5084

[Siedlerchr]

Thank you for reporting this issue. We think, that is already fixed in our development version and consequently the change will be included in the next release.

We would like to ask you to use a development build from https://builds.jabref.org/master and report back if it works for you. Please remember to make a backup of your library before trying-out this version.

Seems good now - also it is nice to have an rpm, managing the Java installs is a pain, so this is definitely welcome (I have been using openSUSE for years now on all my servers). jabref 5 is pretty useable now - I will let you know if I find anymore serious bugs. thanks so much for fixing this. I really do rely upon jabref for my day to day work. I have been trying to get Columbia library to list it - it is the best tool for large bibtex files. I find maintaining a single file is the easiest and then use the aux tool to get the bibtex file for submitting to a journal. best wbm

…

On Sat, Oct 12, 2019 at 4:17 PM Christoph ***@***.***> wrote: Thank you for reporting this issue. We think, that is already fixed in our development version and consequently the change will be included in the next release. We would like to ask you to use a development build from https://builds.jabref.org/master and report back if it works for you. Please remember to make a backup of your library before trying-out this version. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#5411?email_source=notifications&email_token=AAMY3EJNGJ4MBCTDKES4IYTQOIWGHA5CNFSM4I6VBTM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBCHQUI#issuecomment-541358161>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMY3EOWRGQLPOKEPMJU2XTQOIWGHANCNFSM4I6VBTMQ> .

-- W. Bentley MacLeod New York, New York

[Siedlerchr]

Thanks a lot for you feedback! This is really nice to hear.
As we all develop JabRef in our free time we are always happy if users contribute (code, documentation, money)
http://help.jabref.org/en/FAQcontributing