Closed
Bug 521591
Opened 15 years ago
Closed 15 years ago
Shortcuts missing in Mail Toolbar
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: Hb, Unassigned)
Details
Most of the buttons in Mail Toolbar don't show the keyboard shortcuts for them self. Only the buttons under Mark show them correctly.
Sorry, but it's not clear to me what you mean. I can select a message and hit Ctrl+R or Ctrl+L to reply or forward, without those options being explicitly shown in the toolbar buttons. It appears to me that you are referring to the drop-down menus for Get Msgs, Compose, Forward, Next, Print, etc. Some of those may not have shortcuts or may be ambiguous (e.g., Ctrl+L does not distinguish between forwarding inline or as attachment, that's defined by the default).
Comment 2•15 years ago
|
||
(In reply to comment #1) > It appears to me that you are referring to the drop-down menus for Get Msgs, > Compose, Forward, Next, Print, etc. So do I. > Some of those may not have shortcuts or may be ambiguous (e.g., Ctrl+L does > not distinguish between forwarding inline or as attachment, that's defined by > the default). True, but the code already computes which item to show in bold, and that would get the shortcut as well. But the main question is: what do interface guides for the different operating systems say about this? Should drop down menus show shortcut keys or not? Adding our UI tsar...
Comment 3•15 years ago
|
||
As I recall the guidelines say that only the main menu should show the keyboard shortcuts; I believe at one point the context menus used to have them too, but they have at least now all since been removed.
So, then the "Mark" button actually would be wrong. It replicates the top parts of Message > Mark and has the shortcut keys listed for each entry.
INVALID As said, the toolbar dropdowns should NOT show any keyboard shortcuts. So the Mark dropdown is incorrect. Filed in bug 521610
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•