Fixed search result focus handling

[ZodGaz]

Closes #12856
Implemented handleFocus() in FulltextSearchResultsTab , now search results tab shows correctly after a fulltext search, and disappear after the fulltextsearch flag is disabled; fixed also an issue where sometimes the search results tab would be empty after a successful search.

Mandatory checks

• I own the copyright of the code submitted and I license it under the MIT license
• Change in CHANGELOG.md described in a way that is understandable for the average user (if change is visible to the user)
• Tests created for changes (if applicable)
• Manually tested changed features in running JabRef (always required)
• Screenshots added in PR description (if change is visible to the user)
• Checked developer's documentation: Is the information available and up to date? If not, I outlined it in this pull request.
• Checked documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request to the documentation repository.

[trag-bot]

@trag-bot didn't find any issues in the code! ✅✨

[subhramit]

@koppor determine issue number check failed https://github.com/JabRef/jabref/actions/runs/15281990665/job/42983040404?pr=13174

[koppor]

@koppor determine issue number check failed JabRef/jabref/actions/runs/15281990665/job/42983040404?pr=13174

Contributor used Closes [#12856](https://github.com/JabRef/jabref/issues/12865). One out of 10 persons use this strange format. One year ago, we had a help text on it that people should just add the number, or the link - and not both.

NOTE THAT THE LINK POINTS TO ANOITHER ISSUE

• Option A: We try to parse also these kind of things - and also report errors if the link text does not match the issue number
• Option B: Refine the comment text 😅

Update I needed to fix the job name - 5b5cba8

[jabref-machine]

Your pull request needs to link an issue.

To ease organizational workflows, please link this pull-request to the issue with syntax as described in https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue:

Linking a pull request to an issue using a keyword

You can link a pull request to an issue by using a supported keyword in the pull request's description or in a commit message. The pull request must be on the default branch.

• close
• closes
• closed
• fix
• fixes
• fixed
• resolve
• resolves
• resolved

If you use a keyword to reference a pull request comment in another pull request, the pull requests will be linked. Merging the referencing pull request also closes the referenced pull request.

The syntax for closing keywords depends on whether the issue is in the same repository as the pull request.

Examples

• ✅ Fixes #xyz links pull-request to issue. Merging the PR will close the issue.
• ✅ Fixes https://github.com/JabRef/jabref/issues/xyz links pull-request to issue. Merging the PR will close the issue.
• ✅ Fixes https://github.com/Koppor/jabref/issues/xyz links pull-request to issue. Merging the PR will close the issue.
• ❌ Fixes [#xyz](https://github.com/JabRef/jabref/issues/xyz) links pull-request to issue. Merging the PR will NOT close the issue.

[koppor]

Are you sure that this is needed? - I think, Platform.runLater(entryEditor::adaptVisibleTabs) could be directly called - or another method adaptVisisbleTabs() containing this call could be used. focus is wrong IMHO.

[ZodGaz]

Actually is not needed, just tested it. Sorry I'm just starting to get familiar with JavaFX.

[subhramit]

• Option A: We try to parse also these kind of things - and also report errors if the link text does not match the issue number
• Option B: Refine the comment text 😅

None, 1 out of 10 is a bearable edge case. I think this is rarer than 1 out of 10.