Closed Bug 293812 Opened 20 years ago Closed 17 years ago

need shift+ctrl-m shortcut hotkey to create new message in HTML

Categories

(Thunderbird :: Mail Window Front End, enhancement)

x86
Windows 2000
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: wsmwk, Assigned: mscott)

Details

This discussion presumes one's default mail composition preference is set to plain text or "ASK ME". The only way to create a new HTML message (compose window) is to shift left-click on the write/create-a-new-message icon in the main mail window. It is odd that *ONLY* this mail toolbar icon lacks a keyboard shortcut - all other icons have a keyboard equivalent. Lack of this keyboard shortcut is the only item preventing me from removing the mail toolbar to gain some substantial screen real estate (who needs icons when you have the keyboard equivalent?) For consistency, ctrl-N should be be modified as well (not withstanding bug 222020)
I don't see a difference between this bug and the other, altho the text of the report is somewhat different. If I'm missing some subtlety here, feel free to reopen this bug but resummarize it to make it clear what the difference is. *** This bug has been marked as a duplicate of 293814 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Oh, I see -- this one is for Thunderbird.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Severity: normal → enhancement
Version: unspecified → Trunk
As Mike points out in bug 293814 comment 3, there is an acceptable alternative in bug 216132.
QA Contact: front-end
I'm not sure if the direct equivalent of ctrl-shift-m for windows is command-shift-m on the mac, but Bug 428062 may prove that the shortcut key might already be in use. Wayne, would this bug still be valid?
I don't know if 428062 is valid, but I see now the combo is taken. 216132 would be sufficient for me. closing this one INVALID for above reasons
Status: REOPENED → RESOLVED
Closed: 20 years ago17 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.