Remove F1 as standard shortcut for Help
Review Request #128019 - Created May 25, 2016 and discarded
|Albert Astals Cid|
F1 is too important and too easy to trigger for something like Help, that be honest you don't need a shortcut for (since you don't invoke Help that often).
Is there any way to instead change it to an "F1, F1" sequence so that users actively trying to use this still have some easy way to do it, while preventing accidental initiations of help? I'm not sure if that's better for usability or worse though...
As Kai said: Activating the help cursor by pressing F1 (and actually putting useful help behind it!) would be a great thing to have from a user's perspective.
Contextual help would be much more helpful than a plain old help text, and changing the cursor to the help cursor would be a far less annoying unintended action than opening the help browser.
The question is: Do we think there is a chance to get developers to actually put useful contextual help in their UIs in the the future, or will it likely just be doing nothing in the vast majority of apps?
What if people start complaining? ("Why F1 is not working anymore?!?")
I just tried and the shortcut can be disabled globally from system settings (or replaced with another shortcut). It's something that you need to do only once and works for all applications, so it seems a good compromise to me.
While I appreciate the source of this change (I've almost never hit F1 intending to open the doucmentation myself), I don't think a RR is the right place to discuss changes to our default shortcuts. This takes a small survey of a small section of our community. I think the VDG would probably be the best place to have a discussion about what help, if any, is triggered and on what shortcut (though if there is a better source I'm happy to take their input instead). Once there is a consensus, then I'm happy to have those changes implemented.
Since there is a global way to disable F1 for people who find this annoying now, this is a -2 from me. People annoyed at F1 can fix their issue now without code changes while we figure out the best plan forward.