Comment 49 for bug 38753

I started working on drag'n'drop support for Wayland and also looked at a solution for this problem.

This morning I discussed ideas with our usability team and we will also do some iterative in person tests next week during our development sprint.

So far we concluded that the best approach is to implement a raise on hover approach. As soon as the mouse enters another window during drag that one will be raised to give a clear field for the drop.

At the moment the keyboard focus (aka active window) will stay with the window dragged from after the drop. It is difficult to say what the user expects to happen after the drop. Both cases working with the window dragged from and working with the window dragged to are equally possible. The current implementation follows the focus policy: with click to activate the focus stays with the window dragged from, with focus follows mouse the window dragged to will activate.