Closed Bug 766295 Opened 12 years ago Closed 2 years ago

Easier customisation of the message reader header toolbar

Categories

(Thunderbird :: Message Reader UI, enhancement)

13 Branch
x86
All
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: elicoten, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20100101 Firefox/13.0.1 Build ID: 20120614114901 Steps to reproduce: Right Click at the top of the message pane and selected customise. Actual results: No buttons where displayed. Expected results: Should have had a selection of relevant buttons to choose from. In fact, after installing the CompactHeaders extension, many more buttons showed in this list, but why is this in an extension? Surely this should be a core feature?
OS: Windows XP → All
On trunk there is now also a Tag button which isn't on the default set. The default set includes the buttons that are relevant so it's more of a possibility to remove/reorder the buttons to you liking.
Surely there are other buttons that are relevant (obviously not all of these should be on by default though), for example File Print Reply List Mark Next Next Unread Previous Previous Unread Save As and perhaps others.
Severity: normal → enhancement
Component: Toolbars and Tabs → Message Reader UI
Summary: Easier customisation of the mail header toolbar → Easier customisation of the message reader header toolbar

Most of the items you are suggesting are message navigation, which exist in the main mail tool bar above the message list. So I'm not sure we would do this? But I'm not completely sure about the future customization plans, like bug 1773314

Flags: needinfo?(alessandro)

Yeah, this bug is not relevant anymore.
The message header will have a different purpose and context, with a different array of buttons.
The new unified toolbar will offer more in-depth customization to account for various scenarios.

Flags: needinfo?(alessandro)
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.