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.
To repro: 1.Bring up the context menu on the clearcase node. 2.Select 'ClearCase/Find Checked Out Recursively' from context menu 3.Wait for the 'Find Checked Out Recursively' dialog issue 1. The initial focus in not set. User have to press Tab or Shift-Tab to set focus in a element. It would be better to set initial focus on the default button in this information dialog. issue 2. ALT-S does not work. It is possible to move focus in the read-only "Status " textfield via Tab and Ctrl-Tab key, but result of pressing ALT-S is beeping only. The same issues are for ClearCase/Find All Checkout in View and ClearCase/History Text dialogs. Product Version = Sun ONE Studio 5, Standard Edition (Build 030415) IDE Versioning = IDE/1 spec=3.24.1 impl=030415 Operating System = SunOS version 5.8 running on sparc Java; VM; Vendor = 1.4.0_02; Java HotSpot(TM) Client VM 1.4.0_02-b02; Sun Microsystems Inc.
These are problems in the generic output window in vcscore module.
This is quite strange. The menomic for Status is set correctly and the first time the window is opened, ALT-S works. But as soon as the focus is changed, ALT-S stops working. It seems to be consumed by someone else.
In projects build, mnemonics for "Status' is changed to "t". ALT-S is magically consumed by something, but ALT-T works: /cvs/vcscore/src/org/netbeans/modules/vcscore/commands/Bundle.properties,v <-- Bundle.properties new revision: 1.22.30.1; previous revision: 1.22 Is the first issue important? How is the user affected that the initial focus is not set? Everything is accessible by mnemonics. Setting the initial focus on the default button does not make much sense to me. Enter can be used to close the dialog.
Per the Java Look & Feel Design Guidelines: "When opening a dialog box, provide initial keyboard focus to the component that you expect users to operate first. This focus is especially important for users who must use a keyboard to navigate your application." Please see http://webwork.sfbay/products/jlf/ed2/book/index.html Chapter 8, Dialog Box Design for more information. From an accessibility standpoint, a person using an assistive technology such as a screen reader would then be able to enter the text instead of having to press tab to figure out where they are.
This is already fixed in trunk. The focus is on the first component that represents a command option.