windows should raise on click-release not on click

[Zach]

Binary package hint: gnome

Inactive windows should raise on click only after the click is released. Currently they raise on click before the click is released.

This is a usability problem.
Use case:
A nautilus window containing a file to be copied/moved is open. A second, active, nautilus window containing the destination folder is open and partially overlapping the first. If you click and drag the file from the inactive source window, it shouldn't raise to obscure the foreground target window.

With the current behavior, the user must make sure to drag the source and destination windows apart so they are not overlapping in order to ensure the destination will not become obscured by source.

The intent of a click cannot (click and drag vs single click to raise) is ambiguous until the click is released. The current behavior assumes any click in an inactive window is intended to raise the window.

By way of comparison, both Windows and OS X exhibit the "raise on click and release" behavior.

[Roberto Sarrionandia (rbs-tito)]

Is this a bug or a feature suggestion?

[Zach (uid000)]

I'm inclined to classify it as a bug that impacts usability, but I suppose that is subjective.

I believe my corresponding bug for kde got assigned "whishlist".
https://bugs.launchpad.net/ubuntu/+bug/38753

[Sebastien Bacher (seb128)]

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

[frizzle21 (frederik-nnaji)]

i agree totally with this here as a usability problem.
very important feature!! i always have to drag my files down to the windowlist in order to bring the destination window back forward...
that costs a lot of time and makes the whole thing slower.
at least there should be an option to turn such a feature on and off in System>>Preferences>>Windows

Unnecessary to say, this feature is implemented and even standard on other popular desktop operating systems

;)

[Marnanel Thurman (marnanel)]

frederik.nnaji: This bug is a duplicate of bug 29560. Commenting there is likely to have much more effect.