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 463911 - GNOME Panel menus close unexpectedly on specific mouse clicks
GNOME Panel menus close unexpectedly on specific mouse clicks
Status: RESOLVED FIXED
Product: gnome-panel
Classification: Other
Component: menu
2.19.x
Other Linux
: Normal minor
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-06 08:13 UTC by Sebastien Bacher
Modified: 2007-08-22 18:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Sebastien Bacher 2007-08-06 08:13:35 UTC
The bug has been opened on GNOME Panel menus close unexpectedly on specific mouse clicks

"Binary package hint: gnome-panel

When traversing down a Panel menu, the mouse selects the item under the mouse. When traversing up the menu, there is a sort of dead area in which the item under the mouse is NOT selected. For launchers, this is merely a cosmetic error, of one pixel: for folders on the menu, the gap has an additional pixel if the mouse is moved perfectly vertical: if the mouse is quickly clicked on that second, higher, pixel, the menu will disappear! If the mouse remains on the second pixel for a few moments without clicking, or if it is moved horizontally, the selection seems to catch up to the mouse, and there is no problem if you then click.

I found this error in regular use of the menus, however, so it's certainly not arcane! It was rather disconcerting to have my menus close on me for no apparent reason!
..."
Comment 1 Quentin Hartman 2007-08-22 16:56:08 UTC
I am able to reproduce this bug on gnome 2.18.1 (Ubuntu Feisty) but not on Gnome 2.19.6 (Ubuntu Gutsy, updated yesterday). I believe it is fixed in 2.19.6 
Comment 2 Sebastien Bacher 2007-08-22 18:50:48 UTC
closing the bug then, feel free to reopen if somebody still get the issue with the new version though