# Disabling problematic hotkeys
**URL:** https://meta.discourse.org/t/disabling-problematic-hotkeys/96459
**Category:** Bug
**Tags:** keyboard-shortcuts
**Created:** [September 5, 2018, 10:21pm UTC](https://meta.discourse.org/t/disabling-problematic-hotkeys/96459 "2018-09-05T22:21:57Z")
**Posts on this page:** 1
**Showing post:** 7
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [September 6, 2018, 12:26am UTC](https://meta.discourse.org/t/disabling-problematic-hotkeys/96459/7 "2018-09-06T00:26:10Z")
The feature is a bug.
>
When routing an action to a post, we check:
- Do we have a post highlighted with via `j` `k` ? ok, use that
- Do is mouse cursor hovered on a post, ok use that.
This is a recent change introduced via:
> [@Instructions on right and feedback on "wrong" keyboard shortcut usage](https://meta.discourse.org/t/intructions-on-right-and-feedback-on-wrong-keyboard-shortcut-usage/65794):
>
> I knew about the “Keyboard Shortcuts” modal for quite some time, but honestly didn’t know how they worked. Just now, when I investigated a bit further and read some specific instruction by another user, that I first have to j/k in a topic to go through the posts before I could use e and similar, I understood the concept behind it better. Before I tried to combine the keys with alt, ctrl, shift in a random manner and didn’t get any further. Also just hitting e when focusing a post in a topic wit…
The problem it was trying to solve is, "how do I know I can hit `e` and get it to do something?`
The keyboard shortcuts talk about it here:
The original “proposal here” was to pop some help, this is what gmail does:
My call is that the solution of “routing to hovered” does not go anywhere towards teaching, I am also super on the fence about the “teaching” approach here even the one gmail uses.
Like is odd, cause it has some special routing code that does not go through a common path, will sort that out.
---
_[View the full topic](https://meta.discourse.org/t/disabling-problematic-hotkeys/96459)._