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 694189 - menubutton: Make sure the menu shell is deactivated when button toggled
menubutton: Make sure the menu shell is deactivated when button toggled
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: Other
3.7.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2013-02-19 16:49 UTC by Michael Wood
Modified: 2018-04-15 00:30 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
menubutton: Make sure the menu shell is deactivated when button toggled (1.18 KB, patch)
2013-02-19 16:49 UTC, Michael Wood 		none Details | Review

Description Michael Wood 2013-02-19 16:49:19 UTC 
Created attachment 236790 [details] [review]
menubutton: Make sure the menu shell is deactivated when button toggled

If the button is goes inactive and popup menu is visible then de-active the menu shell.

The button state can be changed externally so this helps keep the popupmenu visibility in sync with the button state. This can happen/be tested if the button is togged externally such as by invoking an actionable associated with the button.

Related to bug 694160 (includes a test case which can be applied here too)
Comment 1 Matthias Clasen 2018-02-10 05:07:52 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 2 Matthias Clasen 2018-04-15 00:30:37 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