This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 269268 - Pressing Enter when searching in Navigator does not focus the editor
Summary: Pressing Enter when searching in Navigator does not focus the editor
Status: NEW
Alias: None
Product: platform
Classification: Unclassified
Component: Navigator (show other bugs)
Version: Dev
Hardware: PC Linux
: P2 normal (vote)
Assignee: Jan Peska
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-08 09:09 UTC by Miloslav Metelka
Modified: 2016-12-08 13:53 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Miloslav Metelka 2016-12-08 09:09:29 UTC
Steps to reproduce the problem:
1) Open a java source file with at least one method or field (or create one).
2) Press Ctrl+7 to go to navigator
3) Start to type the method/field name (little floating field appears with the typed name).
4) Press Enter. The floating field disappears but the focus remains in the Navigator.
5) Second press of Enter finally traverses the focus to the editor (it should normally happen after the first press).
Comment 1 Vladimir Voskresensky 2016-12-08 12:03:35 UTC
Some important notes:
- it's worth to have big file with the method body invisible on the screen
Then after step 4 you will see that method now is visible in the editor, but focus remained in the navigator
Previously showing method body in editor and transfer of focus to the editor was atomic from navigator, that's why I think, it's related to the changes done by 
https://netbeans.org/bugzilla/show_bug.cgi?id=268785
Comment 2 Miloslav Metelka 2016-12-08 13:53:22 UTC
Yes, the editor get scrolled so it looks like it grabs the focus but the navigator possibly requests the focus too (possibly the field returns focus to the navigator) and there's some bad timing so that the focus ends in the navigator.
Since the issue #268785 is in fact a one line change I've rolled it back for a while and verified that it's not the culprit of the behavior described here. Not sure if there wasn't some other commit that could cause that so that it would be some bad coincidence.