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.
The explorer tab panes do not follow the JLF guidelines for keyboard navigation. See page 256 of the JLF 2nd edition for a full list. Arrow keys should move focus from one tab to the next. This works once on the explorer, but then focus moves from the content instead of the tab, which is incorrect. The other key binding listed in JLF (cntrl-arrows, cntrl-pgup, pgdn) do not work at all.
Component change: ui -> openide
There is fixed tab navigation via arrows. I don't know what should do the others (C-arrows, C-PageUp/Down). If those are necessary, please reopen the issue. Btw. could you please send a URL to JLF? *** This issue has been marked as a duplicate of 16192 ***
The relevent JLF page is here: http://java.sun.com/products/jlf/ed2/book/Appendix.A15.html#36080 The various control combinations are for navigating between the content pane and the tab, and for changing the among content panes without giving focus to the tabs. I do think this needs to be implemented, but it is possible these are already fixed as part of the other bug.(?)
I'm reopening this but also downgrading it to P4. With the fix in 16192, changing tabs is now possible from the keyboard. However, I still think that the other key bindings should be implemented. The current solution means that the user has to tab through all of the components in order to get focus on the tab. The key bindings needed are: Control-down arrow: Moves from tab to its associated content pane Control-up arrow: Moves from content pane to its associated tab These first two would be very helpful especially for properties sheets, where in order to move focus back and forth from the tab and the other components, the user has to hit the tab key many many times. Control-PgDn: Moves to next content pane (changing the corresponding tab) Control-PgUp: Moves to previous content pane (changing the corresponding tab) These two are less important, but would be nice to have in places where these keybinding aren't used for something else. Note that in the explorer, these key bindings won't work anyway, because the same keybindings are already implemented for the JTree. The key bindings could be implemented for other tabbed panes, like properties sheets, where components in the content pane don't bind these keys to anything.
Jan, what you are asking for is not a bug, but rather an ENHANCEMENT. We'll address it in the next release cycle. No time/resource now.
I would like to clarify tab pane navigation key bindings. Why they sometimes don't work in NB. * Ctrl-Up and Ctrl-Down: Should focus JTabbedPane but is also used in JTree. That is why it doesn't work in explorer. * Ctrl-PgUp and Ctrl PgDown: Should switch to next/previous tab but is also consumed by JTree, JTable and JScrollPane. That is why it doesn't work in explorer and property sheet (JScrollPane consumes key stroke). OTOH Ctrl-Up and Ctrl-Down should move focus to tabbed pane in *property sheet*. Now these key strokes are used for invoking same action as Up and Down strokes (move focus to previous/next property button), what I think *is* a bug (hopefully with simple fix).
UI folks please be extremely careful when you're messing with focus navigation. People are complaining the focusibility of the IDE is actually worsening lately.
Focus navigation bugs (not ui folks) mess NB focusability. Which ui folks decision have made focusabitily worse?
I am not blaming UI team, I just want to make sure that everyone knows focus-related issues are extremely complicated and act accordingly
Bug appears again in trunk (Nov 19). Anyway it is duplicate of more general bug 17449. *** This issue has been marked as a duplicate of 17449 ***
Resolved for 3.4.x or earlier, no new info since then -> verified
Resolved for 3.4.x or earlier, no new info since then -> closing.