JDK-6543222 : REGRESSION: BasicPopupMenuUI.MenuKeyboardHelper needs to be per-AppContext
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 7
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2007-04-05
  • Updated: 2011-03-11
  • Resolved: 2007-04-16
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 JDK 7
6u3Resolved 7Resolved
Related Reports
Duplicate :  
Description
This bug is being filed on behalf of ###@###.###.

In Java SE 6 the Swing MenuSelectionManager was made per-AppContext, which according to Chris is a correct fix. However, the class javax.swing.plaf.basic.BasicPopupMenuUI has a static MenuKeyboardHelper, which causes menu accelerators to only work for the first AppContext which creates a menu. The MenuKeyboardHelper needs to be changed to be per-AppContext as well, at which point menu accelerators will work properly again.

This is a high priority bug as it is a regression relative to earlier releases.

Comments
EVALUATION This is a duplicate of 6492266. It is fixed.
16-04-2007

EVALUATION I beleive this is a duplicate of 6492266. Can ###@###.### please confirm? Also, one note: 6544309 claims that 6492266 is not completely resolved. It has yet to be investigated.
11-04-2007

EVALUATION We need more data in the description of the bug usually small runnable test case is enough
09-04-2007