-
Bug
-
Resolution: Won't Fix
-
P3
-
6u18
-
x86
-
solaris_8
FULL PRODUCT VERSION :
java version "1.6.0_18"
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) 64-Bit Server VM (build 16.0-b13, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
- Windows 7 (6.1.7600)
- Also reported on Windows XP
A DESCRIPTION OF THE PROBLEM :
In previous versions of the runtime, it was possible to use the Alt key to trigger menu accelerators in the same manner as other Windows applications. That is, you could press and release the Alt key to activate the accelerators, and then press, for example "F" to open the file menu.
In the current version, pressing and releasing the Alt key highlights all of the window menus, but subsequent key presses do not open the menus. It is now necessary to press Alt+F to open the File menu.
Accelerators were exhibiting the correct behaviour at least as far back as Java 6 update 13.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1) On the Windows platform, run any Java application that has menu accelerator keys under Java 6 update 18.
2) Press and release the Alt key.
3) Press one of the menu accelerator keys.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
At step 2), the menus highlight to indicate that the accelerator key has been invoked.
At step 3), the menu corresponding to the pressed key opens.
ACTUAL -
At step 2), the menus highlight, as expected.
At step 3), no menu is opened.
ERROR MESSAGES/STACK TRACES THAT OCCUR :
(no error)
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
There are two possible workarounds:
1) Use an earlier version of the Java runtime (it has been confirmed to work with at least Java 6 update 13).
2) Press and hold the Alt key, and simultaneously press the menu accelerator key.
The first option is not a viable one for Windows 7 users, and Update 18 is required to resolve some bugs with the JFileChooser. The second option will work, but is unexpected behaviour for some Windows users.
Release Regression From : 6u13
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.
java version "1.6.0_18"
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) 64-Bit Server VM (build 16.0-b13, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
- Windows 7 (6.1.7600)
- Also reported on Windows XP
A DESCRIPTION OF THE PROBLEM :
In previous versions of the runtime, it was possible to use the Alt key to trigger menu accelerators in the same manner as other Windows applications. That is, you could press and release the Alt key to activate the accelerators, and then press, for example "F" to open the file menu.
In the current version, pressing and releasing the Alt key highlights all of the window menus, but subsequent key presses do not open the menus. It is now necessary to press Alt+F to open the File menu.
Accelerators were exhibiting the correct behaviour at least as far back as Java 6 update 13.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1) On the Windows platform, run any Java application that has menu accelerator keys under Java 6 update 18.
2) Press and release the Alt key.
3) Press one of the menu accelerator keys.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
At step 2), the menus highlight to indicate that the accelerator key has been invoked.
At step 3), the menu corresponding to the pressed key opens.
ACTUAL -
At step 2), the menus highlight, as expected.
At step 3), no menu is opened.
ERROR MESSAGES/STACK TRACES THAT OCCUR :
(no error)
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
There are two possible workarounds:
1) Use an earlier version of the Java runtime (it has been confirmed to work with at least Java 6 update 13).
2) Press and hold the Alt key, and simultaneously press the menu accelerator key.
The first option is not a viable one for Windows 7 users, and Update 18 is required to resolve some bugs with the JFileChooser. The second option will work, but is unexpected behaviour for some Windows users.
Release Regression From : 6u13
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.