Details
-
Type:
Bug
-
Status: Closed
-
Priority:
P2
-
Resolution: Duplicate
-
Affects Version/s: 7
-
Fix Version/s: 7
-
Component/s: client-libs
-
Labels:
-
Subcomponent:
-
Introduced In Version:
-
CPU:generic
-
OS:generic
Backports
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2148300 | 6u3 | Mikhail Lapshin | P2 | Closed | 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.
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.
Attachments
Issue Links
- backported by
-
JDK-2148300 REGRESSION: BasicPopupMenuUI.MenuKeyboardHelper needs to be per-AppContext
-
- Closed
-
- duplicates
-
-
- Closed
-