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 671562 - keyhash issue with shift
keyhash issue with shift
Status: RESOLVED DUPLICATE of bug 661973
Product: gtk+
Classification: Platform
Component: Widget: Other
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
: 671260 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-03-07 15:32 UTC by Matthias Clasen
Modified: 2012-10-09 03:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Matthias Clasen 2012-03-07 15:32:55 UTC 
It seems that _gtk_key_hash_lookup is a bit conflicted about shift...

What I am seeing is that the binding for Shift-F10 -> popup-menu that we create in gtkwidget.c is considered an exact match for a F10 press without any modifiers. Not sure if that is intentional or if it was introduced with the last round of os x tweaks.
Comment 1 Matthias Clasen 2012-03-07 15:43:04 UTC 
gtkkeyhash seems like something that is very much testable - we should really set up tests for this.
Comment 2 Matthias Clasen 2012-03-20 04:18:02 UTC 
*** Bug 671260 has been marked as a duplicate of this bug. ***
Comment 3 Yevgen Muntyan 2012-07-27 09:45:43 UTC 
gdk_keymap_translate_keyboard_state() in gtk-2.24 reports Shift as consumed for Shift-Fn combos.

F3:
event->keyval: 65472
event->state: 0x0
keyval: 65472
consumed: 0x6083

Shift-F3:
event->keyval: 65472
event->state: 0x1
keyval: 65472
consumed: 0x6083
Comment 4 Michael Natterer 2012-08-04 23:58:02 UTC 
Evil, will try to have a look next week.
Comment 5 Andrei 2012-08-05 15:40:41 UTC 
This seems to be duplicate of bug 661973
Comment 6 Michael Natterer 2012-10-08 14:15:02 UTC 
Matthias, didn't you fix that?
Comment 7 Matthias Clasen 2012-10-09 03:45:14 UTC 
yes, I thought I did.

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