Open Bug 1619248 Opened 7 months ago Updated 4 days ago

Keyboard shortcut "M" for "Mark read/unread" not shown in Menu and Contextmenu

Categories

(Thunderbird :: Message Compose Window, defect)

defect
Not set
normal

Tracking

(Not tracked)

ASSIGNED

People

(Reporter: c.buhtz, Assigned: lilian.braud, NeedInfo)

References

Details

(Keywords: good-first-bug, ux-discovery)

Attachments

(3 files)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0

Steps to reproduce:

There is a keyobardshort cut "m" that toogles the read status from unread to read and back from unread to read. Works fine.

But it is not shown in the GUI. I would assume that in the "Messages menu" -> "Mark" -> "Unread" / "Read" should the keyboard shortcut visible also.
It is the same for the context menu of a message.

It does seem odd that a short cut is not listed

Keywords: ux-discovery

(In reply to c.buhtz from comment #0)

There is a keyobardshort cut "m" that toogles the read status from unread to read and back from unread to read. Works fine.

Typo: ... "M" that toggles the read status from unread to read and vice versa, back from read to unread.

But it is not shown in the GUI. I would assume that in the "Messages menu" -> "Mark" -> "Unread" / "Read" should the keyboard shortcut visible also.

Absolutely! Thanks for reporting this.

It is the same for the context menu of a message.

Could you elaborate a little bit why you would wish a shortcut to be displayed in the context menu?
Would you consider it helpful if context menu items would generally expose their respective shortcuts?

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

It does seem odd that a short cut is not listed

One of my most frequently used shortcuts when handling large numbers of messages. Also to mark messages as unread when I still want to come back to them later. Surprising because all the other shortcuts are there. Might be easy to fix.

Flags: needinfo?(c.buhtz)
See Also: → 1647654

(In reply to Thomas D. from comment #2)

Could you elaborate a little bit why you would wish a shortcut to be displayed in the context menu?
Would you consider it helpful if context menu items would generally expose their respective shortcuts?

It is like an in-GUI-manual.
When a user is new to an application she/he first click around to find and use the expected features. This is done by context of course. I want to mark a mail unread: Of course I look into the context-menu of a mail and not of a folder or somewhere else.

While using (context)-menus the user also learn the shortcuts of often used menu entries.

"Normal" users do not read manuals or help pages especially for such a simple task like "What is the shortcut for XYZ?".
RTFM! is a utopic and a bad attitude. Users are lazzy and a bit dump - "Thats reallity Greg!" Even developers are users in some cases - just start to reflect your own behaviour as a user.

In a perfect and pink world a GUI is 100% selfdescribing. Of course this is not reallity but we should try to go/develop into this direction.
Exposing ALL existing shortcuts in the GUI is very easy and should taken as a possibility to reach that goal.

For me (and some other developers) it is a general rule: Featuers should appear or should be accessible from all interface-layers of an application. This means for example everything I can setup in a text-config-file should appear also in the Preferences-Dialog of the application - there should be no difference or hidden options. Also everything I can start from the GUI should be startable via keyboard-shortcut etc - I know it does not make sense in all cases. But a developer should think about it and decide.

Flags: needinfo?(c.buhtz)

(In reply to c.buhtz from comment #3)

(In reply to Thomas D. from comment #2)

Could you elaborate a little bit why you would wish a shortcut to be displayed in the context menu?
Would you consider it helpful if context menu items would generally expose their respective shortcuts?

It is like an in-GUI-manual.
When a user is new to an application she/he first click around to find and use the expected features. This is done by context of course.
[snip]
Also everything I can start from the GUI should be startable via keyboard-shortcut etc.

+1 to virtually all of comment 3. C.buhtz, thank you very much for your user feedback.

Status: UNCONFIRMED → NEW
Component: Untriaged → Message Compose Window
Ever confirmed: true
OS: Unspecified → All
Hardware: Unspecified → All
Summary: Keyboard shortcut "m" not shown in Menu and Contextmenu → Keyboard shortcut "M" for "Mark read/unread" not shown in Menu and Contextmenu
Keywords: good-first-bug
Assignee: nobody → lilian.braud
Status: NEW → ASSIGNED

Liscare, I've reviewed your phabricator patch and requested some minor additions. Would you like to finish this off?

Flags: needinfo?(lilian.braud)
You need to log in before you can comment on or make changes to this bug.