Bugzilla

Some thoughts:
- **UX-efficiency** is key for the brand core of Thunderbird: "Make email easier".
- Efficient keyboard access is key for UX-efficiency, especially for enterprise use cases where large message volumes must be handled every day. If you lose just 20 seconds on each one of 100 messages per day by navigating menus and searching for click targets, that's 2000 seconds = 33 minutes lost per day, that's almost 7% of 8 daily working hours wasted. For repetitive tasks, keyboard can be quite literally a thousand times faster.
- Advanced keyboard control is one thing that makes Thunderbird stand out out as a desktop email client - any webmailer can offer some clickable UI.
- **UX-discovery** is key for keyboard efficiency - Obviously, users can only benefit from keyboard shortcuts if they know about them.
- Contextual disclosure of keyboard shortcuts is key for UX-discovery - we can safely assume that no one will ever try to edit a pill going through composition's main menu, which in this case is not even possible:
  - Pill commands have not been linked with the main command controller, so they are not accessible from main menu (select a pill, open edit menu and try: copy/cut/paste/delete/select-all etc. - nothing! That's a bug.)
  - We don't even have entries for all pill commands in main menus (that's an omission).

In a nutshell:
- Contextual UX-discovery of keyboard shortcuts --> Keyboard efficiency --> UX-efficiency --> Thunderbird brand core: "Make email easier"
- ...which is key especially for enterprise use cases
- In view of the pending release, pill context menu is currently the *only* feasible way of disclosing these keyboard shortcuts (nothing in main menu).
- Context menu is a great way of making keyboard shortcuts discoverable exactly when they are needed.

Hints for implementation:
- Reduce noise by visually de-emphasizing keyboard shortcut display on menu items (e.g. grey color) and sufficient horizontal distance (as seen in screenshot of attachment 9159414 [details]).
- Experiment with disclosure variations like tooltips, or only show the keyboard shortcut for the hovered item.
- Long-term: consider pref to display keyboard shortcuts in context menu or not (e.g. pref toggles attribute, CSS shows/hides the shortcuts)

Some thoughts:
- **UX-efficiency** is key for the **brand core of Thunderbird: "Make email easier".**
- Efficient keyboard access is key for UX-efficiency, especially for enterprise use cases where large message volumes must be handled every day. If you lose just 20 seconds on each one of 100 messages per day by navigating menus and searching for click targets, that's 2000 seconds = 33 minutes lost per day, that's almost 7% of 8 daily working hours wasted. For repetitive tasks, keyboard can be quite literally a thousand times faster.
- Advanced keyboard control is one thing that makes Thunderbird stand out out as a desktop email client - any webmailer can offer some clickable UI.
- **UX-discovery** is key for keyboard efficiency - Obviously, users can only benefit from keyboard shortcuts if they know about them.
- Contextual disclosure of keyboard shortcuts is key for UX-discovery - we can safely assume that no one will ever try to edit a pill going through composition's main menu, which in this case is not even possible:
  - Pill commands have not been linked with the main command controller, so they are not accessible from main menu (select a pill, open edit menu and try: copy/cut/paste/delete/select-all etc. - nothing! That's a bug.)
  - We don't even have entries for all pill commands in main menus (that's an omission).

In a nutshell:
- Contextual UX-discovery of keyboard shortcuts --> Keyboard efficiency --> UX-efficiency --> Thunderbird brand core: "Make email easier"
- ...which is **key especially for enterprise use cases / large message volumes**
- In view of the pending release, pill context menu is currently the *only* feasible way of disclosing these keyboard shortcuts (nothing in main menu).
- **Context menu is a great way of making keyboard shortcuts discoverable exactly when they are needed.**

Hints for implementation:
- Reduce noise by visually de-emphasizing keyboard shortcut display on menu items (e.g. grey color) and sufficient horizontal distance (as seen in screenshot of attachment 9159414 [details]).
- Experiment with disclosure variations like tooltips, or only show the keyboard shortcut for the hovered item.
- Long-term: consider pref to display keyboard shortcuts in context menu or not (e.g. pref toggles attribute, CSS shows/hides the shortcuts)

Some thoughts:
- **UX-efficiency** is key for the **brand core of Thunderbird: "Make email easier".**
- Efficient keyboard access is key for UX-efficiency, especially for enterprise use cases where large message volumes must be handled every day. If you lose just 20 seconds on each one of 100 messages per day by navigating menus and searching for click targets, that's 2000 seconds = 33 minutes lost per day, that's almost 7% of 8 daily working hours wasted. For repetitive tasks, keyboard can be quite literally a thousand times faster.
- Advanced keyboard control is one thing that makes Thunderbird stand out out as a desktop email client - any webmailer can offer some clickable UI.
- **UX-discovery** is key for keyboard efficiency - Obviously, users can only benefit from keyboard shortcuts if they know about them.
- Contextual disclosure of keyboard shortcuts is key for UX-discovery - we can safely assume most users will never try to edit a pill going through composition's main menu, which in this case is not even possible:
  - Pill commands have not been linked with the main command controller, so they are not accessible from main menu (select a pill, open edit menu and try: copy/cut/paste/delete/select-all etc. - nothing! That's a bug.)
  - We don't even have entries for all pill commands in main menus (that's an omission).

In a nutshell:
- Contextual UX-discovery of keyboard shortcuts --> Keyboard efficiency --> UX-efficiency --> Thunderbird brand core: "Make email easier"
- ...which is **key especially for enterprise use cases / large message volumes**
- In view of the pending release, pill context menu is currently the *only* feasible way of disclosing these keyboard shortcuts (nothing in main menu).
- **Context menu is a great way of making keyboard shortcuts discoverable exactly when they are needed.**

Hints for implementation:
- Reduce noise by visually de-emphasizing keyboard shortcut display on menu items (e.g. grey color) and sufficient horizontal distance (as seen in screenshot of attachment 9159414 [details]).
- Experiment with disclosure variations like tooltips, or only show the keyboard shortcut for the hovered item.
- Long-term: consider pref to display keyboard shortcuts in context menu or not (e.g. pref toggles attribute, CSS shows/hides the shortcuts)