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 608139 - Maximizing with double-click on title bar takes focus too strongly?
Maximizing with double-click on title bar takes focus too strongly?
Status: RESOLVED DUPLICATE of bug 599181
Product: metacity
Classification: Other
Component: Focus
2.28.x
Other Linux
: Normal major
: ---
Assigned To: Thomas Thurman
Metacity maintainers list
: 639829 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-01-26 11:03 UTC by Krzesimir Nowak
Modified: 2011-01-18 10:14 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Krzesimir Nowak 2010-01-26 11:03:42 UTC
Sorry for strange title - I wondered how to describe it in short and accurate.

Steps to reproduce:
1. Open two windows - for example gnome-terminal and nautilus.
2. Maximize gnome-terminal by double-clicking on title bar.
3. Switch to nautilus by clicking its icon on panel.
4. Hover over one of icons on title bar (minimize to panel, minimize/maximize/quit).

Expected result:
Icon is highlighted, pressing it does its action.

Actual result:
Icon does not react to cursor being hovered over it and clicking on it makes focus is switched to gnome-terminal.

This can be especially nasty in this situation:
1. Open evolution, it probably will be already maximized (if it is not, then use the maximize button)
2. Open gnome-terminal, if it is maximized, then minimize it and maximize it by double-clicking on title bar.
3. Switch to evolution by clicking its icon on panel.
4. Click the 'x' on its title bar.

Expected result:
Evolution is closed.

Actual result:
Gnome-terminal is closed. Nasty!

Double clicking on title bar to minimize it does not have this problems.

Metacity 2.28.0
Comment 1 Owen Taylor 2010-06-09 16:23:07 UTC

*** This bug has been marked as a duplicate of bug 599181 ***
Comment 2 alfred.theorin 2011-01-18 10:14:36 UTC
*** Bug 639829 has been marked as a duplicate of this bug. ***