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 139862 - raise_or_lower breaks with (some) dialogs
raise_or_lower breaks with (some) dialogs
Status: RESOLVED OBSOLETE
Product: metacity
Classification: Other
Component: general
2.7.x
Other Linux
: Normal enhancement
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks: 155452
 
 
Reported: 2004-04-13 01:39 UTC by mjrauhal
Modified: 2020-11-07 12:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description mjrauhal 2004-04-13 01:39:11 UTC 
The raise_or_lower function (aka "Raise obscured window, otherwise lower")
doesn't do anything when an application has a suitable dialog open. A good and
repeatable example is Evolution (1.4.6): If one presses the Send/Receive button,
Evolution pops up a progress dialog. Now, pressing raise_or_lower key has no
effect when either the main window or the dialog are focused, and only resumes
functioning when the dialog has gone away. In this particular use case, it'd be
nice to dump Evolution into the background while it's updating, without having
to minimize it completely.
Comment 1 Rob Adams 2004-04-13 15:43:35 UTC 
So raise/lower would have to walk transient trees and raise/lower the whole set
of windows.  Seems reasonable; not too hard to implement.
Comment 2 André Klapper 2020-11-07 12:36:36 UTC 
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all
old feature requests in Bugzilla which have not seen updates for many years.

If you still use metacity and if you are still requesting this feature in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/metacity/-/issues/

Thank you for reporting this issue and we are sorry it could not be implemented.