Bug 132339 - Starting a drag from an inactive window shouldn't bring it to the front (bis)
Starting a drag from an inactive window shouldn't bring it to the front (bis)
Status: RESOLVED INVALID
Product: gtk+
Classification: Platform
Component: .General
3.3.x
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
:
Depends on: 80984
Blocks:
  Show dependency tree
 
Reported: 2004-01-23 23:00 UTC by Julien Olivier
Modified: 2011-12-02 14:49 UTC (History)
6 users (show)

See Also:
GNOME target: ---
GNOME version: 2.21/2.22

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Julien Olivier 2004-01-23 23:00:50 UTC 
See bug #41681 for details.

In fact this bug was closed by fixing sawfish. As
sawfish is not GNOME's default window manager
anymore, I guess Metacity has to be fixed too.

I'll submit a bug to metacity too.
Comment 1 Gregory Merchan 2004-02-03 00:50:47 UTC 
Pending resolution of the Gtk+ bugs on which bug #133047 depends,
which are targeted for Gtk+2.6, this should be an easy fix.
Bug #133037 is the important one for Nautilus.
Comment 2 philipp strack 2005-01-25 10:32:21 UTC 
I Think Severity should be raised to major. Because this Bug makes is extremly
annoing to all kind of users and it makes DnD in nautilus extremly difficult to
use. Afaik we need Drag and Drop every time we want to copy or move a File. This
Bug forces us to first rearrange the nautilus windows everytime. From my point
of view this is not only a very big usability issue but a Major loss of
functionality.
Comment 3 kenden 2008-06-09 14:48:56 UTC 
I still finds this annoying in Gnome 2.22.
Comment 4 Julien Olivier 2010-07-16 08:12:45 UTC 
Well, it's still very annoying in GNOME 2.30 :)
Comment 5 Cosimo Cecchi 2011-12-01 22:49:09 UTC 
No need to keep track on this in nautilus. Any solution to this will need to be addressed at the toolkit level.
Comment 6 Julien Olivier 2011-12-02 09:18:10 UTC 
(In reply to comment #5)
> No need to keep track on this in nautilus. Any solution to this will need to be
> addressed at the toolkit level.

I re-opened it against GTK+ then. Or should I open a new one instead?
Comment 7 Cosimo Cecchi 2011-12-02 14:23:43 UTC 
(In reply to comment #6)

> I re-opened it against GTK+ then. Or should I open a new one instead?

There are several already, see e.g. https://bugzilla.gnome.org/show_bug.cgi?id=133037
Comment 8 Julien Olivier 2011-12-02 14:49:58 UTC 
OK, sorry.
Note You need to log in before you can comment on or make changes to this bug.