• Auto-detect identifier type when opening New Entry dialog with clipboard content
• Refactored identifier detection logic to use Identifier API consistently
• Fixed text field binding to use correct field for identifier input
• Improved fetcher initialization and null-safety checks

Fix identifier auto-detection and field binding issues

• Moved getDialogPane().disableProperty().bind() from constructor to initialize() method to
 ensure proper initialization order
• Fixed clipboard text handling in finalizeTabs() to set text on idText field instead of
 interpretText field
• Removed duplicate clipboard extraction logic from initializeLookupIdentifier() method
• Refactored updateFetcherFromIdentifierText() to add null-safety check and improved readability
• Removed extractIdentifierFromClipboard() helper method as logic is now integrated into main flow
• Added clipboard content initialization in initializeLookupIdentifier() with proper null and
 newline checks
• Improved idFetcher.setOnAction() callback with null-safety check before accessing fetcher value

jabgui/src/main/java/org/jabref/gui/newentry/NewEntryView.java

Document identifier selection bug fix

• Added entry documenting the fix for identifier selection not working on fresh start
• References issue #15000

CHANGELOG.md

Description

The identifier field is now pre-filled with any single-line clipboard text, even when it is not a
recognized identifier. Because lookup validation only checks for non-blank input, users can
accidentally trigger fetch attempts (network calls) with arbitrary clipboard content, leading to
confusing errors and unnecessary requests.

Code

jabgui/src/main/java/org/jabref/gui/newentry/NewEntryView.java[R331-338]

+        String clipboard = ClipBoardManager.getContents().trim();
+
+        if (!StringUtil.isBlank(clipboard) && !clipboard.contains("\n")) {
+            idText.setText(clipboard);
+            idText.selectAll();
+
+            Platform.runLater(() -> updateFetcherFromIdentifierText(clipboard));
+        }

Evidence

NewEntryView pre-fills the identifier text field for any single-line clipboard content; lookup
execution does not validate that the text is a real Identifier (it only checks non-blank), so
arbitrary clipboard content can be sent to fetchers/composite fetcher.

jabgui/src/main/java/org/jabref/gui/newentry/NewEntryView.java[331-338]
jabgui/src/main/java/org/jabref/gui/newentry/NewEntryViewModel.java[118-123]
jabgui/src/main/java/org/jabref/gui/newentry/NewEntryViewModel.java[248-259]
jabgui/src/main/java/org/jabref/gui/newentry/NewEntryViewModel.java[262-282]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`NewEntryView.initializeLookupIdentifier()` currently pre-fills the identifier input (`idText`) from *any* single-line clipboard content. However, identifier lookup execution accepts any non-blank string, so users can unintentionally trigger network lookups with random clipboard text (e.g., a sentence), leading to confusing failure dialogs and unnecessary requests.
### Issue Context
- The prefill is guarded only by `!blank` and `!contains("\n")`.
- Lookup workers (`WorkerLookupId`, `WorkerLookupTypedId`) do not validate that `idText` is a syntactically valid `Identifier`; they only check non-blank.
### Fix Focus Areas
- jabgui/src/main/java/org/jabref/gui/newentry/NewEntryView.java[331-338]
- jabgui/src/main/java/org/jabref/gui/newentry/NewEntryViewModel.java[118-123]
- jabgui/src/main/java/org/jabref/gui/newentry/NewEntryViewModel.java[248-282]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools