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.
I have noticed in recent dev builds (JDK 7, Gnome, Ocean) that Ctrl-PageUp and Ctrl-PageDown cycle not only through document windows (as in Firefox etc.), but also through "tool" windows in other modes, e.g. Projects/Files/Services. I am not sure if this is intentional or not. 1. I was under the impression that all tool windows were supposed to be accessed via the Window menu or Ctrl-<number> shortcuts. They are not available e.g. using Ctrl-TAB (Ctrl-~). 2. Ctrl-PageUp/Down have bindings in Swing list/tree views that are sometimes useful. In particular, if I have dozens of projects open and I want to multiselect a handful of nonadjacent projects in the Projects tab (e.g. for some VCS operation), I would previously select the first one, then use Ctrl-{Up/Down/PageUp/PageDown} to move to the next one (Ctrl-Space to select), etc. Now Ctrl-Up/Down still work to move the focus without changing selection, but Ctrl-PageUp/Down switch me to a different tab instead. So I need to use Ctrl-Up/Down to move around, which can be much slower if moving by a screenful or two. I don't consider this a major use case, but it is something I definitely used before and have missed.
Probably not a high priority, but should be evaluated.
Passing back.
moving opened issues from TM <= 6.1 to TM=Dev
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. We apologize for any inconvenience. Thank you. The NetBeans Team
Still an issue in current releases. Was never made clear if this was a deliberate design decision or a mistake.
cc-ing "olangr" from HIE team. Ondro, could you please evaluate this and propose the solution which we should follow? Please try to think about this together with issue #163611. Thanks.
I personally don't see this as an a11y issue but rather a functionality issue. True it does affect keyboard navigation of the product, but even so it is not a matter of making the product more/less accessible IMO.