Closed Bug 1986124 Opened 11 months ago Closed 11 months ago

Single-key keyboard shortcuts should be abolished

Categories

(Thunderbird :: Untriaged, defect)

Thunderbird 140
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 615957

People

(Reporter: jake, Unassigned)

Details

Steps to reproduce:

  1. Start new message (on 2nd monitor)
  2. Click back on folders window to check previous messages
  3. Not realize that 'new message' window was no longer active (using Windows, which makes it harder to tell)
  4. Start typing

Actual results:

Messages disappeared in an unrecoverable manner, since it was not known what keypresses caused what action.

Expected results:

Nothing, or an alert that "you have a message window open", but that wouldn't help if I began to type into a non-TB window I thought was active.

Keyboard shortcuts should require pressing of a control key, such as Ctrl or Alt, along with the key. It is far too easy to lose or misplace important emails as things are, and this should be rectified.

Ref: https://www.reddit.com/r/Thunderbird/comments/t76lhr/how_to_disable_single_key_keyboard_shortcuts_in/

The addon 'tbkeys-lite' that could solve the problem fails to install (silently), and looks like a PITA to configure anyway.

The plan is to provide this capability via bug 615957, which unfortunately is not yet available. There is no plan to disable keys prior to it's implementation.

Status: UNCONFIRMED → RESOLVED
Closed: 11 months ago
Duplicate of bug: 615957
Resolution: --- → DUPLICATE

(In reply to Wayne Mery (:wsmwk) from comment #1)

The plan is to provide this capability via bug 615957, which unfortunately is not yet available. There is no plan to disable keys prior to it's implementation.

*** This bug has been marked as a duplicate of bug 615957 ***

I found that after logging this, which is indeed a duplicate.

I've made a couple of comments there. If I was familiar with the development environment, I would be willing to implement a fix along the lines proposed, as it should be straightforward. But setting up the development environment would likely take forever (particularly on Windows), so I can't.

You need to log in before you can comment on or make changes to this bug.