Open Bug 540571 Opened 12 years ago Updated 6 years ago

Print condensed / short comma-separated list of attachments below other headers (instead of one line per attachment -> waste of paper)

Categories

(MailNews Core :: Printing, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

People

(Reporter: dswirsky, Unassigned)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [GS] Outlook parity)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 GTB6 (.NET CLR 3.5.30729)
Build Identifier: version 2.0.0.23 (20090812)

When printing an email that has one or more attachments, the names of the attachments are listed on separate lines at the end of the printout.  If only the first page of a multi-page email with attachments is printed, the attachments are not listed at all in the printout.  I would like to suggest that when an email is printed, that the names of the attachments always be listed on the first page at the end of the header block, with multiple attachment names listed on each line (this is the way Outlook does it).  A short email message with many attachments will thus print on a single page rather than on two or more pages.  This will also save paper.

Reproducible: Always

Steps to Reproduce:
1. Find an email with one or more attachments.
2. Print the email.
3.
Actual Results:  
The names of the attachments are listed on separate lines at the end of the printout.
This looks like bug https://bugzilla.mozilla.org/show_bug.cgi?id=443634, would you agree that the goals of both bugs are unique, printing emails with attachment list taking less paper ?
Yes, bug 443634 discusses the issue.  What this bug 540571 adds is a specific way to address the issue.  Bug 443634 suggests providing a simple list of attachments, but does not describe what the list should look like.  This bug 540571 describes what the list should look like.
Printout design proposal of this bug (clarification)
dswirsky, is this what you want?

Subject: ...
From: ...
Date: ...
To:...
Attachments: Attachment1 [details] [diff].doc, Attachment2 [details] [diff].doc, Attachment3 [details] [diff].doc, 
Attachment4 [details] [diff].doc, Attachment 5 [details].doc
Bugzilla's over-zealous autolinkification logarithms messed up what was supposed to look like this:
Attachments: Attach_ment1.doc, Attach_ment2.doc, ...
OS: Windows XP → All
Hardware: x86 → All
Yes. Exactly.
New summary to better describe this bug's enhancement goal.

This looks like valid RFE -> confirming. This provides the shortest possible list of attachments in the same way as Outlook does (per comment 0). It's *one* possible way of addressing bug 443634.

NEW status doesn't mean that this is accepted or wanted yet as a print layout.
Blocks: 443634
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: When printing email, attachments are listed on separate lines at the end of the printout. → When printing a message, there should be a condensed / shorter comma-separated list of attachments below other headers (instead of long list with one line per attachment at the end of printout -> waste of paper)
Whiteboard: Outlook parity
Component: General → Printing
Product: Thunderbird → MailNews Core
QA Contact: general → printing
Whiteboard: Outlook parity → [GS] Outlook parity
Summary: When printing a message, there should be a condensed / shorter comma-separated list of attachments below other headers (instead of long list with one line per attachment at the end of printout -> waste of paper) → print condensed / short comma-separated list of attachments below other headers (instead on one line per attachment -> waste of paper)
Summary: print condensed / short comma-separated list of attachments below other headers (instead on one line per attachment -> waste of paper) → Print condensed / short comma-separated list of attachments below other headers (instead of one line per attachment -> waste of paper)
Removing myslef on all the bugs I'm cced on. Please NI me if you need something on MailNews Core bugs from me.
You need to log in before you can comment on or make changes to this bug.