-
Bug
-
Resolution: Unresolved
-
P3
-
9, 10
See the email http://mail.openjdk.java.net/pipermail/swing-dev/2014-December/004085.html
--------------------
The fix looks good. The root cause of this error is that mouseExited is not fired on the focused container when a modal dialog is shown. I'm surprised that there isn't a linked issue against AWT to either fix the toolkit to fire the mouseExited (via the Z axis) on modal dialog, suppress the 2nd call to mouseEntered after dialog is closed, or fix the MousListener documentation to state that how the mouse cursor enters or leaves a component has some exceptional conditions. My preference would be to fire mouseExited on modal dialog shown.
--------------------
--------------------
The fix looks good. The root cause of this error is that mouseExited is not fired on the focused container when a modal dialog is shown. I'm surprised that there isn't a linked issue against AWT to either fix the toolkit to fire the mouseExited (via the Z axis) on modal dialog, suppress the 2nd call to mouseEntered after dialog is closed, or fix the MousListener documentation to state that how the mouse cursor enters or leaves a component has some exceptional conditions. My preference would be to fire mouseExited on modal dialog shown.
--------------------
- relates to
-
JDK-6219960 null reference in ToolTipManager
-
- Resolved
-