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 766429 - Finishing drag and drop immediately after drag-leave causes drag-drop failure
Finishing drag and drop immediately after drag-leave causes drag-drop failure
Status: RESOLVED INVALID
Product: gtk+
Classification: Platform
Component: Widget: Other
3.18.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2016-05-14 10:43 UTC by Kestrel
Modified: 2018-02-12 08:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Kestrel 2016-05-14 10:43:11 UTC 
When dragging and dropping it is possible for the last signal before attempting to drop to be drag-leave which will cause drop to fail unexpectedly. No drag-drop signal occurs as there was no immediately prior drag-motion to test if drop is possible, the only way for drop to succeed after drag-leave is if there is another drag-motion.

To ensure that dropping doesn't fail in this way, drag-leave should always be followed immediately by drag-motion or alternatively the previous drag-motion should be used to determine if drop is possible.

See downstream Firefox bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1269282

Ubuntu 16.04 libgtk-3-0:amd64 3.18.9-1ubunt
Comment 1 Matthias Clasen 2018-02-10 05:10:07 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 2 Kestrel 2018-02-12 08:03:50 UTC 
On further investigation with Ubuntu 17.10 this bug only affects Unity.