JDK-5056076 : keyboard focus problem with Jmenu
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 1.4.2_03
  • Priority: P3
  • Status: Closed
  • Resolution: Won't Fix
  • OS: solaris_8
  • CPU: sparc
  • Submitted: 2004-06-02
  • Updated: 2008-12-18
  • Resolved: 2008-12-18
Related Reports
Relates :  
Relates :  
Description
The customer is facing issues with the Jmenu and the internalframes when using swing. Basically if there are 2 internalframes with the same mnemonics,
then changing the focus from one internal frame to another using the
mouse does not change the keyboard focus.

 The attached test case displays this fact more clearly. In the test case, create 2 internal frames. Both of them have the same menu 'File' which can be popped up using the Alt+f mnemonic.
 Focus on internal frame 1 and then click to popup the File menu. Without closing the menu, now shift the focus to the internal frame 2  (using the mouse click). If we use the mnemonic Alt+f, we observe that the File menu of the internal frame 1 popups even though the focus is on internal frame 2.
I have tested this behavior on 1.4.2_03 and 1.4.2_05 and the problem persists.  However we do not see any problem on 1.5 beta-1 (meaning the mnemonic opens up
the menu for the internal frame which has the focus.)
The problem is also seen consistently seen on Windows 2000. We think there is problem in JInternalFrame itself where the "lastFocusOwner" is not getting recycled properly. 

Comments
EVALUATION Name: sh120115 Date: 06/02/2004 Two things about this bug: 1) We should contact the submitter for the test case as they forgot to attach it. 2) The submitter suggests that this problem doesn't exist in tiger-beta1. Perhaps we've already fixed it, but we should confirm that. ###@###.### 2004-06-02 ====================================================================== The bug is reproducible on 1.4.2_05. The bug is not reproducible on 1.5.0-beta3-b54. ###@###.### 2004-06-03 The bug is escalated for 1.4.2xx. Hence reopening the bug. ###@###.### 2004-06-22
03-06-2004