-
Enhancement
-
Resolution: Duplicate
-
P4
-
None
-
1.0.1, 1.0.2, 1.1.5, 1.1.6, 1.2.0
-
generic, x86, sparc
-
generic, solaris_2.5.1, solaris_2.6, windows_nt
========
Everyone knows how to pop down (cancel) a menu. You just click anywhere
outside the menu, and it goes away, right? Not so with Swing menus, unfortunately.
Currently Swing menus only pop down if you click outside the menu but inside the
JFrame parent of the popup menu. This is because the AWT does not provide a way
to observe mouse events outside the java application's windows, leaving us no
way to find out (at the java level) that the user has clicked elsewhere on the
desktop. As a result, swing applications feel 'different' from native apps.
This is a BadThing(tm).
- duplicates
-
JDK-4137341 Clicking outside of the appl does not take down a menu
-
- Closed
-
-
JDK-4106331 menus don't go away unless java window is clicked
-
- Closed
-
-
JDK-4127064 Heavyweight JPopupMenus obscure other applications
-
- Closed
-
-
JDK-4155684 App follows mouse movement in the background
-
- Closed
-
-
JDK-4156858 pulled-down menu doesn't unpost when window is no longer active.
-
- Closed
-
-
JDK-4185431 Menu selection platform inconsistency
-
- Closed
-
-
JDK-4176725 Clicking frame border doesn't close open menus.
-
- Closed
-
-
JDK-4143416 Window will not capture input from other frames.
-
- Closed
-
-
JDK-4290715 Grab/Release Capture
-
- Closed
-