After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 595354 - Drag-leave/Drag-drop event is not fired when the drop is unsuccessful on KDE
Drag-leave/Drag-drop event is not fired when the drop is unsuccessful on KDE
Status: RESOLVED INCOMPLETE
Product: gtk+
Classification: Platform
Component: Widget: Other
2.17.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2009-09-16 12:49 UTC by cool.rajat
Modified: 2017-11-22 09:45 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Source of the application (9.89 KB, text/x-c)
2009-09-16 12:49 UTC, cool.rajat 		Details
Executable of the attached application (15.95 KB, application/octet-stream)
2009-09-16 12:50 UTC, cool.rajat 		Details

Description cool.rajat 2009-09-16 12:49:36 UTC 
Created attachment 143271 [details]
Source of the application 

When Drag-leave event is not fired when we leave the drop target on KDE . 

1. Run the attached Application 
2. Drag the Drag-me button to the drag Destination and leave the destination
with out dropping the target.
3. Both Drag-motion and drag-leave events are obtained.
4. Drag some file from desktop to the button labelled "drag dest" on the gtk
application and leave destination without dropping  .
5. On KDE Only drag-motion event is fired. No drag-leave event is obtained.
where as on Gnome both events are obtained.

Expected: drag-leave event should be obtained.
Comment 1 cool.rajat 2009-09-16 12:50:36 UTC 
Created attachment 143272 [details]
Executable of the attached application
Comment 2 Alexandre Franke 2016-11-27 14:44:20 UTC 
Hey, are you still experiencing such issues with GTK+ 3?
Comment 3 Alexandre Franke 2017-11-22 09:45:46 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!