Summary | printing messages |
Queue | IMP |
Queue Version | Git master |
Type | Enhancement |
State | Resolved |
Priority | 1. Low |
Owners | slusarz (at) horde (dot) org |
Requester | rsalmon (at) mbpgroup (dot) com |
Created | 12/28/2010 (5306 days ago) |
Due | |
Updated | 01/18/2011 (5285 days ago) |
Assigned | |
Resolved | 01/18/2011 (5285 days ago) |
Milestone | |
Patch | No |
Assigned to Michael Slusarz
State ⇒ Resolved
(hide sidebar and top/bottom menus) ?
the entire screen and it is not officially supported by us. I added
the print CSS to dimp to keep it somewhat backward-compatible with
DIMP 1.x. IMP has never had special print formatting.
Bug #9475: ID 0 is a valid MIME IDhttp://git.horde.org/horde-git/-/commit/f57f36ae85d4bda99beda581c0282a38682418ec
New Attachment: imp.pdf
not that difficult to add a bit of CSS formatting to remove the most
obtrusive UI-specific elements.
Is it possible to do the same when user is using traditional mode ?
(hide sidebar and top/bottom menus) ?
New Attachment: email.eml
HTML parts with blocked images, those images will remain blocked for
printing purposes until the user manually unblocks the images.
Printing using the provided part links does this automatically.
parts will be broken on certain browsers. For an example, see the
two documents I have attached. "good-html" is printed using the
print link for the part. "bad-html" is the output of printing the
entire page.
not that difficult to add a bit of CSS formatting to remove the most
obtrusive UI-specific elements.
But understand that printing the entire page is still not going to be
"officially" supported by us, due to the following shortcomings:
1. The page may continue to contain UI elements. For example, for
HTML parts with blocked images, those images will remain blocked for
printing purposes until the user manually unblocks the images.
Printing using the provided part links does this automatically.
Another example - you will see the Show/Hide quoted block widgets when
printing a text part. Again, printing using the print links will not
show these items.
2. As mentioned multiple times below, messages with inline HTML parts
will be broken on certain browsers. For an example, see the two
documents I have attached. "good-html" is printed using the print
link for the part. "bad-html" is the output of printing the entire
page.
Ticket #9475: Basic print formatting from popup message screenhttp://git.horde.org/horde-git/-/commit/0b8ec8bcf692ff2e46191f3dac57b11f4f24b776
New Attachment: print.zip
more than one inline part that needs to be printed? In almost every
case, there is *ONE* part of the message that needs to be printed.
So in almost every case, clicking print for a part is exactly what
is intended.
this one later on.
What an end user will expect, is it to be able to print (at least) a
simple message (only one part). And not just the body of the message
but the header as well: info like From, To, Date.
The attached example is a single part only message (sent to the dev
list) and will illustrate what we expect (I hope).
git-DIMP : using git DIMP, I doubled clicked on the message and use
the print function of the browser (in my case FF).
old-DIMP: using an older version and the provided print function.
yahoo: I redirected the message and used the provided print function.
gmail: I redirected the message and used the provided print function.
To me, the better looking output is old-DIMP.pdf. It has what anyone
can expect the header and the body of the message.
The git-DIMP output doesn't print the full message. We can see as well
buttons like Reply, Forward, Delete...
to open each part of a message in different windows to print them!
more than one inline part that needs to be printed? In almost every
case, there is *ONE* part of the message that needs to be printed. So
in almost every case, clicking print for a part is exactly what is
intended.
State ⇒ Feedback
should be a print button to open in a view that will print properly.
breaks printing the entire message (I understand this doesn't happen
on all browsers, but that's exactly the point. The UI has to be
consistent across browsers - printing an email at home vs. at work
should not produce two different outputs).
The only viable solution (outside of remove the HTML IFRAME code,
which isn't going to happen) is to print individual parts only. I
believe there was discussion about this when I made the changes (last
February) and no other solution was provided. Thus, the links to
print each part since it is the ONLY way to reliably print a part.
(like IMP used to have) which open a message (ready to print) in a
new window.
to the previously mentioned IFRAME issue. Gmail doesn't use IFRAMEs
and instead converts the HTML message into a series of DIVs that are
individually formatted. Of course it probably took a software
engineer (or group of engineers) 6 months to develop this code, and
they don't seem to be sharing it with others, so this is not a viable
solution.
to open each part of a message in different windows to print them!
State ⇒ Accepted
be a print button to open in a view that will print properly.
work anymore - this is due to several IE/Firefox limitations that
prevent mail messages longer than one page from printing properly.
impossible to make it work. That why my original request was to re-add
the print link feature.
I've checked gmail and yahoo mail, and they both have a print button
(like IMP used to have) which open a message (ready to print) in a new
window.
open each part of a message in different windows to print them!
anymore - this is due to several IE/Firefox limitations that prevent
mail messages longer than one page from printing properly. The only
way to work around is to print EACH PART in a separate window.
New Attachment: imp.zip
I've attached output from new and old IMP.
printing using older IMP (print link) looks nice.
printing using newer IMP => output looks like anything but a message.
New Attachment: email-old.pdf
possible through CSS in IMP 5 too.
attached output is printing using actual git version. Buttons like
forward, reply, view source shouldn't appear.
State ⇒ Rejected
possible through CSS in IMP 5 too.
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ printing messages
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ New
This was really handy since we can't have a good looking output if
printing using browser's print button.
Any chance of adding back this feature ?