JDK-6181145 : PIT: ALT + SPACEBAR does not bring up the frame's default menu when focus is in disabled button
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2004-10-19
  • Updated: 2011-01-19
  • Resolved: 2005-07-12
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6 b43Fixed
Related Reports
Relates :  
Relates :  
Description
The following bug fix 
5044469: REG: Disabled component gains focus and receives keyevents on win32
suppresses the events for space bar when a button is disabled and still has the focus. In such cases, when we press ALT + SPACE, the events for SPACE is suppressed hence preventing the frame from showing it's default menu containing maximize, restore, close options. Default frame menu should not be suppressed.

This is reproducible only in the following PIT build on win32. Not reproducible on any of the previous mustang / tiger builds.
java version "awt.pit-jcg-win-03-2004-10-15-Fri-int.mustang"
Java(TM) 2 Runtime Environment, Standard Edition (build awt.pit-jcg-win-03-2004-10-15-Fri-int.mustang)
Java HotSpot(TM) Client VM (build 1.6.0-ea-b08, mixed mode)

I have attached a sample test. Execute the sample test. You would see a frame with a button. Click the button. The button will be disabled but will still have the focus. Now press 'ALT + SPACE'. If you don't see frame's default menu coming up, the bug is reproduced.
###@###.### 10/19/04 12:37 GMT

Comments
EVALUATION A Win32 only affected. Should check for modifiers too. ###@###.### 10/19/04 12:50 GMT Taking 5044469 fix apart will correct this bug in JDK6.0b43. ###@###.### 2005-06-30 13:02:22 GMT
19-10-2004