GNOME Bugzilla – Bug 710388
Menu navigation triangle doesn't work anymore
Last modified: 2018-05-02 15:49:30 UTC
The navigation triangle is basically what is also described in http://bjk5.com/post/44698559168/breaking-down-amazons-mega-dropdown To reproduce: - run a program with submenus, like the menu example of gtk3-demo (this only affects submenus that open to the right) - hover over a menu entry with a submenu - move your cursor diagonally to the last entry of the submenu so that it crosses the item below the currently active one in the first level of the menu -> This causes the item below the currently active one to be selected while in 3.8 this was not the case and one could easily navigate to the submenu I've bisected the code and it looks like e8b38fedbd8961df4aaaa75b122a06ddc68e75f2 was the commit that broke it.
Created attachment 339870 [details] [review] Fixes submenu navigation triangle This issue was caused when mouse coordinates were changed to floating point values. This patch floors the event->x_root and event->y_root values when setting the navigation region.
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.
This is still an issue with Gtk+ apps that use a traditional menubar. As it is, using a Gtk+ 3 app's menubar is much less ergonomic than with apps using Qt or even Gtk+ 2!
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/450.