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 536664 - Message Box select/focus/z-order problem
Message Box select/focus/z-order problem
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: Other
unspecified
Other All
: Normal major
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2008-06-04 17:55 UTC by Matthew
Modified: 2018-04-15 00:28 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matthew 2008-06-04 17:55:12 UTC
Please describe the problem:
When a message box is displayed, it does not behave in the same way as a dialog box in terms of selecting it and its parent window, or how it appears in the alt-tab list (especially in KDE).  In KDE, alt-tabbing to an app displaying a message box gives the unresponsive parent window focus and doesn't show the message box if it's hidden, making it look like the whole app has hung.  In GNOME, the message box is rendered visible but it should get focus, not the parent window.


Steps to reproduce:
1. run an app producing modal message boxes
2. Get it to produce a message box
3. Try alt-tabbing and clicking, and compare the behaviour with that of a dialog box.


Actual results:
See problem description.  Sorry not to provide a specific example, but it manifested itself in a wxGTK app I am developing.  You can try "Dialog and Message Boxes" in gtk-demo which is more complicated (three windows are displayed) but still allows you to compare the behaviour of the two different child windows.

Expected results:
Same behaviour for message boxes as for dialogs.

Does this happen every time?
Yes.

Other information:
This bug has been around for a while - I thought it was in wx and reported it there a year or so ago.
Comment 1 Alexandre Franke 2017-11-05 21:24:07 UTC
Is this still an issue with GTK+ 3?

Was that happening only in KDE? Also with GTK+ directly and not only with wxGTK?
Comment 2 Matthias Clasen 2018-04-15 00:28:39 UTC
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new