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 144526 - Should not iconify a task which is active when clicked but not in view
Should not iconify a task which is active when clicked but not in view
Status: RESOLVED DUPLICATE of bug 90134
Product: libwnck
Classification: Core
Component: general
unspecified
Other Linux
: Normal major
: ---
Assigned To: libwnck maintainers
libwnck maintainers
Depends on:
Blocks:
 
 
Reported: 2004-06-17 12:31 UTC by Salman Khilji
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Salman Khilji 2004-06-17 12:31:02 UTC
From:  <>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.6.0
Subject: Should not iconify a task which is active
when clicked but not in view

Distribution: Fedora Core release 2 (Tettnang)
Package: gnome-panel
Severity: normal
Version: GNOME2.6. 2.6.x
Gnome-Distributor: Red Hat, Inc
Synopsis: Should not iconify a task which is
active when clicked but not in view
Bugzilla-Product: gnome-panel
Bugzilla-Component: Window List Applet
Bugzilla-Version: 2.6.x
Description:
Description of Problem:

When I left click on a task which has an active
window at the time of
the click, but the window is not completely in
view, the task is
iconified instead of bringing it to the front. 
This basically requires
that a user clicks the task button twice instead
of once to bring it to
the front.  GNOME is inconsistant with other
environment and is
confusing and distracting in my opinion in this
respect.

Steps to reproduce the problem:
1. In Preferences, select Windows
2. Make sure the 'Select windows when the mouse
moves over them" is  the
only option checked
3. Click Close.
4. From Accessories, choose calculator
5. Move the calculator to the lower right of the
desktop, but leave some
space between the Panel and the Calculator window
(This assumes that
your Panel is in the default location as shipped
in Fedora Core 2.
6. From Accessories, choose character map
7. Resize the character map window so that it is
smaller than your
calculator window.
8. Move the Character map window to the lower
right of the desktop area
is such a way that almost all of it is hidden and
only a small portion
of it is visible below the calculator window. (See
the screenshot at
http://web.tampabay.rr.com/skhilji/GNOME.png)
9. Move your cursor on top of your calculator
window and vertically move
it to the Panel with an intention of bringing the
Character Map window
to the front.
10.  Right before you click on the Character Map
tasklist button, you
will see that the Character Map window is active
because of our "Select
windows when the mouse moves over them" option and
the mouse cursor was
over the window for a fraction of a second before
we got to the Panel.
When you click the Character Map tasklist button,
you will see that it
is iconified.  You have to click it again to bring
it to the front.

Actual Results:

Clicking the tasklist button iconifies is first. 
Clicking it again
brings it to the front


Expected Results:

Clicking the tasklist button should bring it to
the front because the
window is not in view and is not the top-most
window.  Clicking it again
to iconify it


How often does this happen?

Everytime


Additional Information:

Switching from KDE, I can tell you that this
behavior in GNOME is not
acceptable. KDE does it right.  See screenshot at 
http://web.tampabay.rr.com/skhilji/KDE_Example.png.
 In the KDE example,
the Konqueror window is active, but not top-most.
 If I click the
Konqueror button on the taskbar, it becomes the
top-most window. 
Clicking it subsequent times iconifies it.  The
default behavior of
GNOME is distracting and confusing since when I
click on the taskbar
window, I need to see my window coming to the top
immediately.  This bug
is related to 79500 but not quite the same.  If
the developers do not
want to fix this, then I at least want bug # 79500
back!
Comment 1 Elijah Newren 2004-10-19 22:51:12 UTC

*** This bug has been marked as a duplicate of 90134 ***