JDK-7129762 : [macosx] Regression of 4874092: dragExit() fired outside of a drop site
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 7
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: os_x
  • CPU: x86
  • Submitted: 2012-01-13
  • Updated: 2018-09-05
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.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-4874092 - dragEnter/dragExit methods of DragSourceListener fire without reaching target
Description
Run the test closed/java/awt/dnd/NoTargetNoDragExitTest: it does check if dragExit() is not called if the mouse is not dragged over any drop site. Tests fails.
Comments
- this is an issue reported against 7(7u), - there are now affected version 9 filed for this issue - 7u issues are transferred to Sustaining Nevertheless if someone have a report against 9 - please reopen and add affectedVersion 9 or 7u specific escalations might be reopen to Sustaining
10-08-2014
EVALUATION Looks like latest DnD rework did not fixed this problem. Right now we see any component as a potential drop target and generating dragExited every time we criss the border of the component. I admit that this is a problem but i don't think it quelifies as a P3 and hence i lower its priority. Will try to fix it in 7u6.
01-02-2012
EVALUATION I'm working on optimizing the DnD event generation and this should be fixed with bunch of other DnD problems when i'm done. Will check it again when i'm done with DnD rework.
24-01-2012