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 86956 - Too easy to set unmodified keys as bindings.
Too easy to set unmodified keys as bindings.
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: [obsolete] Keybinding
git master
Other other
: High minor
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-07-01 03:08 UTC by Ben FrantzDale
Modified: 2006-01-22 11:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gcc-unmodified-keys.patch (1.07 KB, patch)
2006-01-17 17:12 UTC, Bastien Nocera
none Details | Review
gcc-unmodified-keys-2.patch (2.23 KB, patch)
2006-01-19 14:34 UTC, Bastien Nocera
committed Details | Review

Description Ben FrantzDale 2002-07-01 03:08:28 UTC
I found it far too easy to set unmodified keys (such as 'space' and 'f') to
be bound. I can imagine any of the `F*' keys being used unmodified, along
with 'PrtSc', 'ScrLk', and 'Pause', but other than that, I think the
potential for massive confusion is too great.

My suggestions: Either (a) have a dialog come up when a user tries to give
an unmodified letter key or (b) just give a beep when the user tries to
give an unmodified letter key. Or perhaps (b) for the first time, then (a)
if the user is being persistant. Also (a) could be done by printing a
warning to the box the user expcts to see the shortcut show up in.
Comment 1 Luis Villa 2002-07-02 10:36:14 UTC
Yeah, good call, Ben.
Comment 2 Luis Villa 2002-11-07 14:37:23 UTC
SPAM as discussed last night. Search for 'SPAM as discussed last night' to catch
these all and delete them. :) 
Comment 3 Jody Goldberg 2004-04-07 14:45:10 UTC
This is a good idea.
I'll commit a patch immediately after we branch
Comment 4 Vincent Noel 2004-10-05 19:53:57 UTC
ping : does your patch still apply ?
Comment 5 Sebastien Bacher 2005-01-02 17:51:42 UTC
any news on this ?
Comment 6 Christian Kirbach 2005-07-13 14:17:35 UTC
Jody: has sth been commited?
I do  not see an attached patch.
Comment 7 Bastien Nocera 2006-01-17 17:10:29 UTC
Asking the user would be a real bummer.

It should be easy enough to blacklist, or whitelist a certain number of keys, but I'm afraid of causing problems for people that don't use latin-like keyboards.
Comment 8 Bastien Nocera 2006-01-17 17:12:09 UTC
Created attachment 57542 [details] [review]
gcc-unmodified-keys.patch

Example patch, the blacklisting needs to be much much chunkier obviously.
This patch only reverts if any upper latin letter is typed on its own.
Comment 9 Bastien Nocera 2006-01-17 17:12:59 UTC
I can finish this patch off with what I think is right, and we could then wait for bug reports...
Comment 10 Rodrigo Moya 2006-01-18 11:47:49 UTC
Please Bastien, finish the patch :)
Comment 11 Bastien Nocera 2006-01-19 14:34:00 UTC
Created attachment 57642 [details] [review]
gcc-unmodified-keys-2.patch

The dialogue, and its text probably suck a bit, would probably need HIG love as well. We refuse to bind main letter keys (or at least what I think are main letter keys) for:
- Latin
- Japanese
- Arabic
- Cyrillic
- Greek
- Hebrew
- Thai
- Korean/Hangul
Comment 12 Rodrigo Moya 2006-01-20 10:26:18 UTC
the patch looks ok to me, if it works, so commit as you wish. I guess you'll have to warn translators about the string change though.
Comment 13 Bastien Nocera 2006-01-22 11:55:00 UTC
2006-01-22  Bastien Nocera  <hadess@hadess.net>

        * gnome-keybinding-properties.c: (accel_edited_callback):
        Refuse to bind letter keys without a modifier (Closes: #86956)

Only took 3.5 years to fix ;)

bug 328152 asks for a better error message.