Thunderbird:Compact Message Header:Use Cases

In Thunderbird 3, bug 480623 moves compact header view to an extension. Please list use cases where compact header is helpful and/or normal message header gets in the way. A use case in this context should ideally include a specific type of user, a specific type of mail, and circumstances or work flow implications. The purpose is to collect information which will later be organized, discussed, and used toward the end goal of a) improving how compact header view is supported, and b) helping specific use cases where improving compact header is not sufficient to significantly improve the use case.

The "need" for vertical space and your passion for the need are of course assumed, and so should be omitted from the use case (see #Notes_and_Assumptions). Discussion and promoting one's position beyond the specifics is a non-goal. A short one or two sentence description limited to how the message pane is used in a specific case will be most helpful.

Use Cases

• Generally, being able to see as much of a message's body as possible without being forced to scroll! Vertical space should be of primary importance!

• Very many (most?) users read their e-mails in the preview pane. Giving them a non-sucky experience should be a priority.

• Reading e-mails, which are typically taller than the preview pane. Showing as much as possible and minimizing scrolling is critical.

• Viewing photos from family & friends, which are typically taller than the preview pane. Users should be able to see at least one *full* photo without scrolling.

• Reading newsletters, which are always longer than the preview pane is tall.

• Reading newsgroup threads, which are typically taller than the preview pane.

• bugmail - for a triager processing incoming bugmail most of the standard header information is not useful (To/From, etc), often much of the top of a bugmail is not very useful, and extensions like bugmail extension need a couple lines to display bug details from mail header and other sources (eg bugzilla). Reducing header space would result in less initial scrolling of each bugmail, which is often done in large batches.

• E-cards that show web-like content (where content is more important than UI)

• Newsgroups graphics (stationery) posts that assume a larger viewing window. As compared to OE, we offer an 8% reduction in size.

• Users of previously composed Templates will have to adjust for the new smaller viewing window.

• The problem pertains to standalone window as well as the preview pane. I think that there are more users using the standalone model as opposed to the preview pane, as is commonly understood.

• Implementing Bug # 499516 IMO would be the best of both worlds. Showing the header pane where appropriate and helpful, and hiding it when not needed.

Notes and Assumptions

• Compact header view would be less needed if the normal header were kept to a minimum or if it scrolled with the message.

References

• [API doc] (not yet available)
• bug 480623 - move compact message header view to an extension