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.
Standard way how to get focus out from component which consumes TAB key (JTextArea, JTable, ...) is to press CTRL+TAB. This works in IDE but not if such component is in modal dialog. Cause: NbFocusManager doesn't delegate key events to DefaultFocusManager when the key event source component is in modal dialog. Comment says that it fixes #500 and #2483. But CTRL+TAB is handled in DFM so these bugs should be fixed some other way.
Another focus issue from NbFocusManager. This stuff should be realy rewriten, not only because of jdk1.4. Assigning.
updating subcomponent
I found next problem with JTabbedPane in modal dialog. It is unable to move to inner component of TabbedPane by pressing TAB. This bug in NbFocusManager is blocking accessibility.
Dusan for many times I heard you say "it's NbFocusManager". The focus system in JDK is known for its bugginess and has been redesigned/rewritten in JDK 1.4. Can it be the case here too?
I really think that it's bug in NbFocusManager. I tried described functionality without installed NbFocusManager and then with it. Without NbFocusManager (exactly without raw number 91) I could go out from JTextArea by press CTRL+TAB and I could to move to inner component of TabbedPane by pressing TAB too. BUT it is not working with actual NbFocusManager (with raw 91). I don't know exactly if this raw and modal-condition around could be removed, but if yes (without any side effects), then I vote for removing :) I think that similar bug exists because of NbFocusManager (Yes there I used phrase "becase of NbFocusManager" too :) >>> Issue #15960 BAD TAB order in modal dialogs. I provide the same small test with and without raw 91 in NbFocusManager with the same result.
*** Issue 15181 has been marked as a duplicate of this issue. ***
Adding 'A11Y' keyword.
I will need to verify tables in jar packager are fixed when this fix is integrated.
After thinking overnight I decided to raise this to P2 since it makes accessibility testing more difficult and this bug is broadly replicated across the IDE. Fix seems manageable based on evaluation thus far...it appears this can be fixed in the netbeans focus manager. Testing is more difficult because automated tool cannot tab past the table. If someone wants to knock this back to P3 or change target to later release I defer to your judgement. Thanks, Steve
I strongly agree with the priority change. The control+tab problem cripples the keyboard accessibility across the IDE.
I think this is fixed since fix for 15960 was integrated. I have tested it (JDK1.3) and haven't found any component where Ctrl+Tab doesn't work.
verified in [nb_release33](200112040330) on [jdk1.3.1](01) and [jdk1.4](88) / Solaris (CDE) and Windows 2000
Resolved for 3.4.x or earlier, no new info since then -> closing.