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.
[dev sep 23, but has been true for a long time] Perhaps this is already reported, but I am reporting it to try to bring some pressure to get it fixed. In MDI mode (at least for me: Linux + Enlightenment; JDK 1.3.1; but also observed on Windows), if you have keyboard focus on the Explorer (thick border on nodes), then select a main menu item via keyboard shortcut, after the menu is closed the Explorer will still be selected (active border) but the selected node will have the thin border and the Explorer has no keyboard focus (arrow keys etc.). There are other serious keyboard focus bugs I encounter when using the keyboard with the IDE, but this is the most serious as it occurs all the time, and necessitates constant mouse clicking to give focus back to the Explorer. FYI other serious bugs observed in MDI with the keyboard but complicated to reproduce include: after virtual desktop or window focus switch with keyboard, sometimes the last-selected (editor) window is now unselected according to title bar but still has keyboard focus, and clicking on it selects it but makes it lose keyboard focus permanently and must be closed and reopened; sometimes the Explorer is selected and has the thick border, but is unresponsive to keyboard events, and that tab must be closed and reopened to work; sometimes after Enlightenment desktop switch the Editor window is still activated but has no cursor and no keyboard focus until clicked on; sometimes random keyboard shortcuts such as Ctrl-2 or Ctrl-3 or Shirt-F10 do not work for a while, until some different window is clicked on and then they are fine.
Dusan, could you look at it?
This bug also affects context-sensitive help, though currently help IDs for many menu items are not mapped to help topics.
Patrick aren't you thinking of some other bug? This is about opening a menu, selecting some item, menu closes, then no KB focus in normal parts of the IDE. If you are thinking of the fact that KB shortcuts do not work while a menu is selected, that is some entirely different bug (which I think I also filed long ago).
You're right, Jesse. It's bug 9425 I'm worried about.
Problems with KB focus in the Explorer have gotten much worse in recent builds. With [dev oct 11 MDI] I find it necessary very frequently to click on Explorer tabs to get focus; often this even does not work and I have to close and reopen tabs. After switching tabs via Alt-Left generally I have no KB focus on the new tabs. (Occasionally after closing Workplace by the way the tab is reopened with the correct root node but no children. This does not always happen, not sure how to reproduce, probably a separate bug.) I'm not sure what changed recently but it is a regression IMHO from already bad behavior. The Explorer is becoming very difficult to use without a mouse.
> Problems with KB focus in the Explorer have gotten much worse in > recent builds. With [dev oct 11 MDI] I find it necessary very > frequently to click on Explorer tabs to get focus; often this even > does not work and I have to close and reopen tabs. After switching > tabs via Alt-Left generally I have no KB focus on the new tabs. > ... > I'm not sure what changed recently we used to disallow the handles of tabbed pane to get focus, a listener is used to immediately turn the focus to the newly selected (tabbed) component. Now the handles must be focusable for some A11Y reasons I don't understand. If this is the cause then how ironic...
Jesse, the two bugs you originally reported have been fixed. This one is actually a duplicate of the other two bugs.
Including the worst one, lost KB focus on Expl. due to focus on handles of tabbed pane (assuming this is really the cause)? I still see that regularly as of dev nov 7. If I see it again starting now I will file a fresh bug and try to describe how to reproduce it (not easy: it happens routinely but I see no particular pattern).
verified in [nb331_dev](200201100331)
Resolved for 3.4.x or earlier, no new info since then -> closing.