Comment 51 for bug 38753

Revision history for this message
In , Get-sonic (get-sonic) wrote :

(In reply to Martin Gräßlin from comment #42)
>
> 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.

I'm not sure if that'd suffice. Consider the situation:
1. The 'source' window is behind the 'destination' window initially
2. The source window would cover the destination window completely if it is raised
3. Because the source window is behind the destination window initially, the destination window is visible
4. Now the user wants to drag something from the source window to the destination window
5. The user starts to drag some item from the source window.
6. If the source window is raised, the destination window is no longer visible so 'hovering' over it is not possible!

PS: I am extremely happy to see this bug being worked up on. Thanks a million for all the great work you guys are doing.