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 673906 - [regression] Context menus: menu item selected (blue) after right-clicking -> accidentally clicking the selected menu item
[regression] Context menus: menu item selected (blue) after right-clicking ->...
Status: RESOLVED DUPLICATE of bug 591258
Product: gtk+
Classification: Platform
Component: Widget: GtkMenu
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
: 672802 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-04-11 13:35 UTC by Volker Sobek (weld)
Modified: 2014-03-04 15:28 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Volker Sobek (weld) 2012-04-11 13:35:26 UTC
(Filing a new bug here and marking the old one as duplicate because the old one was TL;DR and one can easily reproduce it with gtk3-demo-application.)

How to reproduce:
- run gtk3-demo-application
- write some text
- mark some text
- right click
  -> context menu opens, with first menu item 'Cut' not selected (correct
  behavior)
- click on the 'Cut' or 'Copy' menu entry

After that, the first menu entry will always be selected after right-clicking, provided the menu entry 'Cut' is active (= you have text selected).

I some applications the first entry of the right-click menu is always selected, even right after starting the application (like nautilus).

This happens with context-menus in every application I have tested so far: nautilus, evolution, totem, gnome-terminal ... and is a serious usability issue because 'slow' right-clicks trigger the first menu item.

Affected are gtk+ 3.2 and 3.4 (haven't tested 3.0).
Comment 1 Volker Sobek (weld) 2012-04-11 13:36:15 UTC
*** Bug 672802 has been marked as a duplicate of this bug. ***
Comment 2 Lars Karlitski 2014-03-04 15:28:01 UTC

*** This bug has been marked as a duplicate of bug 591258 ***