shortcuts can override normal keyboard input

Bug #1221515 reported by Cory
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Switchboard Keyboard Plug
Fix Released
High
Julien Spautz

Bug Description

While fiddling with settings, I managed to set one of my keyboard shortcuts ("Windows -> Maximize") to "Space".

Next time I sat down to use my machine, I was surprised to find that my spacebar wasn't working.
It took 20min of troubleshooting (including plugging in a spare keyboard) to figure out what had happened.

Allowing basic input keys to be overridden like that is a bad user experience. I effectively "broke" my environment with a single setting. The obvious solution is to disallowing the basic alphanumeric character set, as well as tab, space, enter, and punctuation, to be overridden as shortcuts when unmodified. It seems like basically anything I would use to enter text into into a text field should be "safe", but I'm not sure where you want to draw the line here.

This bug reminds me of Alex Limi's excellent article on why the "disable javascript" button doesn't belong in Firefox: http://limi.net/checkboxes-that-kill

Thanks so much for your hard work. I love Luna.

Revision history for this message
Julien Spautz (julien-spautz) wrote :

This also works with some other keys like "enter" or "."

I guess shortcuts should always require a modifier key, e.g. shift, ctrl, and super, as I can't think of any exception.

Changed in switchboard-plug-keyboard:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Julien Spautz (julien-spautz)
Changed in switchboard-plug-keyboard:
status: Confirmed → In Progress
Revision history for this message
Larry (timefordrums) wrote :

If you always require a modifier, extra keys on gaming keyboards will not be able to be used as efficiently.

Changed in switchboard-plug-keyboard:
milestone: none → loki-beta1
Cody Garver (codygarver)
Changed in switchboard-plug-keyboard:
milestone: loki-beta1 → loki-alpha1
status: In Progress → Fix Committed
Revision history for this message
Vojtěch Hauser (vojtech-hauser) wrote :

I don't really think you can do it simply by disabling keys without telling the user what is going on. For example I just tried to set shortcut for screenshot to PrtSc button which is disabled - I had no idea why every time I pressed PrtSc "Disabled" appeared. But then I noticed that Ctrl+Print worked so I said to myself: "Aha! Let's make a bug report!".

1) Let the user set any key to anything they want and provide them with a option to reset given key to its default value so if the user sets space to anything else than space then they can just go to keyboard settings and reset the space key to its default value. If you'd like to go bulletproof add reset to default button to every command as well. Also a way to reset all keys/commands at once would be a useful feature.
2) If you think that it's a good idea to disable certain keys, make it tell the user that the key they've pressed is disabled and that it's not a good idea to use it (make it feel like a feature rather than a bug) but give them an option (checkbox or anything) to use it anyway because people use many odd shortcuts (especially in the Custom section!) and they're not happy if you force them to change their habits.

Cody Garver (codygarver)
Changed in switchboard-plug-keyboard:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.