Disabling problematic hotkeys

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:

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:

image

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.

2 Likes