Open
Bug 427474
Opened 17 years ago
Updated 2 years ago
Email print out should show email account information
Categories
(MailNews Core :: Printing, enhancement)
MailNews Core
Printing
Tracking
(Not tracked)
NEW
People
(Reporter: tonyoh888, Unassigned)
References
(Depends on 1 open bug)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 2.0.50727; .NET CLR 1.1.4322; Media Center PC 4.0)
Build Identifier: version 2.0.0.12 (20080213)
The print out of thunderbird should show out the email account of the user who printed out this email on top and underline it as same as microsoft outlook for easy to reference.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Potentially a duplicate of bug 14985, which is however asking for the user name only to be added to the printout. This RFE is for the full account, if there are multiple accounts for a user that are to be distinguished.
I couldn't find any duplicate that would exactly match this request, but some clarification might be needed. I don't think that just imitating the Outlook appearance should be the aim here. Currently, the account name and e-mail address are shown at the first page of the print-out, as part of the header section, but not on any following page. If "Print Background" is enabled in the Page Setup, this is enhanced by a gray box underneath the headers.
If your primary aim is to have the account information printed on every page, this is suggested in bug 118766 comment #1 by replacing the internal mailbox URL information with a more useful account/folder pair.
Comment 3•17 years ago
|
||
Confirming, sounds quite useful.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Adding some dependencies as mentioned in my previous comments.
Component: General → MailNews: Printing
Product: Thunderbird → Core
QA Contact: general → printing
Version: unspecified → Trunk
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•