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 615022 - Main Menu applet: un-selectable menu items on menus that are larger than the screen height
Main Menu applet: un-selectable menu items on menus that are larger than the ...
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkMenu
2.19.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2010-04-06 23:15 UTC by Sameer Morar
Modified: 2018-04-15 00:07 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sameer Morar 2010-04-06 23:15:38 UTC
Description:	Ubuntu lucid (development branch)
Release:	10.04
gnome-applets:
  Installed: 2.30.0-0ubuntu1
  Candidate: 2.30.0-0ubuntu1

Steps to reproduce:

1) Right click on a free area in the panel and choose "Add to panel..."
2) Select "Main Menu" (NOT Menu Bar!!), and click Add
3) Click on the Main Menu Icon, and locate the longest menu (probably System->Preferences)
4) Resize screen resolution to ensure that the longest menu does not fit in the screen
5) Try to launch any item on the menu below the scroll area

What happens:
When the mouse enters the scroll area, the menu scrolls down.
However, when the mouse leaves the scroll area, the menu scrolls up, and the last visible menu item (without any scrolling) is highlighted.
It appears to be impossible to launch menu items below the scroll area using the mouse.

What is meant to happen:
When the mouse leaves the scroll area, the menu should not scroll up, and visible menu items should be highlighted by the mouse.

It is possible to select these menu items using the keyboard, so the bug appears to be something to do with the mouse leaving the scroll area.
Comment 1 Sebastien Bacher 2010-04-29 21:15:43 UTC
the issue is a gtk one when using a theme setting gtk-auto-mnemonics on, reassigning to gtk
Comment 2 Daniel Boles 2017-08-29 23:37:30 UTC
Is this still reproducible? If so, please can we have a minimal test case that doesn't depend on an old application? Thanks.
Comment 3 Matthias Clasen 2018-04-15 00:07:04 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