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 722814 - Unable to close top-level window if popup visible
Unable to close top-level window if popup visible
Status: RESOLVED WONTFIX
Product: gtk+
Classification: Platform
Component: Widget: Other
3.11.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2014-01-23 05:02 UTC by Daniel Wyatt
Modified: 2014-01-23 06:09 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Daniel Wyatt 2014-01-23 05:02:57 UTC
It seems if there is a GTK_WINDOW_POPUP visible and I try to close the top-level window it belongs to, nothing happens.

The quickest way to see this behavior is with the standard file chooser dialog's type-ahead find:
1) Pop open a file chooser dialog (I opened gedit and hit CTRL+O)
2) Type in the treeview so the type-ahead find popup window shows up
3) Attempt to close the file chooser dialog via the close button
4) Nothing happens :(
Comment 1 Matthias Clasen 2014-01-23 05:23:18 UTC
That is the nature of menus and such popups under X11: they take a grab.
We will probably move some of these over to the newly merged GtkPopovers, which is an alternative to menus that does not have this problem.
Comment 2 Daniel Wyatt 2014-01-23 06:07:55 UTC
(In reply to comment #1)
> That is the nature of menus and such popups under X11: they take a grab.

I was afraid of that.

> We will probably move some of these over to the newly merged GtkPopovers, which
> is an alternative to menus that does not have this problem.

Interesting, thanks for the info (and amazingly quick reply). I just took a look at the GtkPopovers demo and it looks promising.
I guess that will be the long term solution here.
I'm not sure what I'll do right now, I don't think I have the option of using this bleeding-edge code (trying to fix https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1271605).

Anyways, I guess I'll close this since the behavior is known and intended.