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 232105 - [New Project Wizard] Cannot jump to next control via "TAB"-key when in filter field
Summary: [New Project Wizard] Cannot jump to next control via "TAB"-key when in filter...
Status: RESOLVED DUPLICATE of bug 234064
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 7.4
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-01 20:42 UTC by markiewb
Modified: 2013-08-12 20:53 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description markiewb 2013-07-01 20:42:05 UTC 
[ BUILD # : 7.4beta ]
[ JDK VERSION : 1.7.0_21 ]

In 7.4 there is a new filter field in the "New Project"/"New File" wizards. 
When the focus is in this textfield, then...

ACTUAL: pressing "tab"-key won't jump to the next GUI control
EXPECTED: presisng "tab"-key will jump to the next GUI control
Comment 1 markiewb 2013-07-01 20:42:39 UTC 
Also CTRL-TAB won't work
Comment 2 Milos Kleint 2013-07-02 05:56:41 UTC 
(In reply to comment #1)
> Also CTRL-TAB won't work

Ctrl-tab works for me on win7 + Build 201306162301 + 1.7.0_21
Comment 3 Milos Kleint 2013-07-02 05:57:28 UTC 
(In reply to comment #2)
> (In reply to comment #1)
> > Also CTRL-TAB won't work
> 
> Ctrl-tab works for me on win7 + Build 201306162301 + 1.7.0_21

but that means "go to the outer tab cycle", so that's not a solution IMHO
Comment 4 markiewb 2013-07-02 06:09:05 UTC 
Strange thing. I tried it yesterday using Win7 64bit, dev build from yesterday and JDK 1.7.0_25 and it didn't work
Comment 5 markiewb 2013-07-02 06:11:42 UTC 
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > Also CTRL-TAB won't work
> > 
> > Ctrl-tab works for me on win7 + Build 201306162301 + 1.7.0_21
> 
> but that means "go to the outer tab cycle", so that's not a solution IMHO

AFAIK tab switches to next focusable widget, ctrl-tab switches to previous focusable widget (regarding to tab order)
Comment 6 Milos Kleint 2013-07-02 06:19:47 UTC 
(In reply to comment #5)
> (In reply to comment #3)
> > (In reply to comment #2)
> > > (In reply to comment #1)
> > > > Also CTRL-TAB won't work
> > > 
> > > Ctrl-tab works for me on win7 + Build 201306162301 + 1.7.0_21
> > 
> > but that means "go to the outer tab cycle", so that's not a solution IMHO
> 
> AFAIK tab switches to next focusable widget, ctrl-tab switches to previous
> focusable widget (regarding to tab order)

No, that's Shift-Tab
Comment 7 markiewb 2013-07-02 06:30:07 UTC 
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #3)
> > > (In reply to comment #2)
> > > > (In reply to comment #1)
> > > > > Also CTRL-TAB won't work
> > > > 
> > > > Ctrl-tab works for me on win7 + Build 201306162301 + 1.7.0_21
> > > 
> > > but that means "go to the outer tab cycle", so that's not a solution IMHO
> > 
> > AFAIK tab switches to next focusable widget, ctrl-tab switches to previous
> > focusable widget (regarding to tab order)
> 
> No, that's Shift-Tab

You are right. My fault. Sorry Milos for the confusion. Tab and Shift-Tab.
Could you reproduce the issue using a new dev build and a new jdk u25?

I will also try to reproduce this issue at work using a different system configuration.
Comment 8 Milos Kleint 2013-07-02 11:35:31 UTC 
QuickSearch.SearchTextField appears to be doing stuff with focus roots because it attempts to swallow escape character. I believe the isManagingFocus() method is crucial here for the Tab functionality, if I comment it out Tab starts working properly.

reassigning to platform/awt
Comment 9 Stanislav Aubrecht 2013-08-12 15:27:54 UTC 
Seems to be already fixed in #234064
Comment 10 markiewb 2013-08-12 20:53:08 UTC 

*** This bug has been marked as a duplicate of bug 234064 ***