JDK-8068809 : [macosx] MouseDragged event is fired only once
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 8u25,9
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: os_x
  • CPU: x86
  • Submitted: 2015-01-11
  • Updated: 2015-01-13
  • Resolved: 2015-01-13
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 9
9Resolved
Related Reports
Duplicate :  
Description
FULL PRODUCT VERSION :
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)

ADDITIONAL OS VERSION INFORMATION :
OS X 10.10.1 

EXTRA RELEVANT SYSTEM CONFIGURATION :
Standard Mac mini

A DESCRIPTION OF THE PROBLEM :
The mouseDragged event is fired only once when the mouse is dragged on a Panel component. This disables the dragging of the underlying component.

REGRESSION.  Last worked in version 7u45

ADDITIONAL REGRESSION INFORMATION: 
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
see here: https://bugs.openjdk.java.net/browse/JDK-8061636

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Component should receive mousedragged events.
ACTUAL -
Component receives mousedragged event only once

ERROR MESSAGES/STACK TRACES THAT OCCUR :
No error message.

REPRODUCIBILITY :
This bug can be reproduced always.

---------- BEGIN SOURCE ----------
See here: has been reported on OpenJDK ; https://bugs.openjdk.java.net/browse/JDK-8061636
---------- END SOURCE ----------

CUSTOMER SUBMITTED WORKAROUND :
No workaround other than switching back to Java 7