Print.css

Good Day;
I have spent several hours backfilling my html knowledge, specifically
on the link attribute. As I understand it, when I print (or print
preview), a different css file is supposed to be used because there is a
link line with media=“print” in it. When I chase this farther, the css
file it should be using is print.css. The contents of print.css
indicate to me that it should not show a number of div id’s and classes
that refer to the the ticket metadata when printing.
However, when I try to print a ticket, all of the ticket metadata does
show up and occupies about a page before the body of the ticket is
printed.
I have tried to find any documentation on the wiki and google, what
little reference I have found has me thinking it should work as is.
Clearly I am missing something, could someone point me at something that
will explain how to take advantage of the print.css file?
Bob Miller
334-7117/660-5315
http://computerisms.ca
bob@computerisms.ca
Network, Internet, Server,
and Open Source Solutions

The contents of print.css
indicate to me that it should not show a number of div id’s and classes
that refer to the the ticket metadata when printing.
However, when I try to print a ticket, all of the ticket metadata does
show up and occupies about a page before the body of the ticket is
printed.

The print stylesheet does need some updating for 4.0 and could use some
all around love to make it much more friendly, but that ticket metadata
was always meant to print. It’s basic information about the ticket that
people expect to see.

(The selectors you’re seeing are referencing chrome around the ticket
metadata, not the metadata itself.)

Thomas

Thomas,

I don’t want to look like an idiot, but I have been using RT since 3.4 and
have never seen a print option, under tools or whatever. Is it an extension
or plugin? How do I find it and what does it do?

Kenn
LBNLOn Tue, Jul 19, 2011 at 11:00 AM, Thomas Sibley trs@bestpractical.comwrote:

On 07/19/2011 01:45 PM, Bob Miller wrote:

The contents of print.css
indicate to me that it should not show a number of div id’s and classes
that refer to the the ticket metadata when printing.
However, when I try to print a ticket, all of the ticket metadata does
show up and occupies about a page before the body of the ticket is
printed.

The print stylesheet does need some updating for 4.0 and could use some
all around love to make it much more friendly, but that ticket metadata
was always meant to print. It’s basic information about the ticket that
people expect to see.

(The selectors you’re seeing are referencing chrome around the ticket
metadata, not the metadata itself.)

Thomas


2011 Training: http://bestpractical.com/services/training.html

I don’t want to look like an idiot, but I have been using RT since 3.4
and have never seen a print option, under tools or whatever. Is it an
extension or plugin? How do I find it and what does it do?

Print stylesheet are applied by your browser on top of the normal
stylesheets when you choose to print the web page from your browser.
The printing part isn’t RT specific, only the print.css stylesheet that
RT ships with.

Thomas

Thomas,

I’ll have to give it a try and see what happens. Thanks.

Kenn
LBNLOn Tue, Jul 19, 2011 at 11:57 AM, Thomas Sibley trs@bestpractical.comwrote:

On 07/19/2011 02:47 PM, Kenneth Crocker wrote:

I don’t want to look like an idiot, but I have been using RT since 3.4
and have never seen a print option, under tools or whatever. Is it an
extension or plugin? How do I find it and what does it do?

Print stylesheet are applied by your browser on top of the normal
stylesheets when you choose to print the web page from your browser.
The printing part isn’t RT specific, only the print.css stylesheet that
RT ships with.

Thomas


2011 Training: http://bestpractical.com/services/training.html

Thanks Thomas

The contents of print.css
indicate to me that it should not show a number of div id’s and classes
that refer to the the ticket metadata when printing.
However, when I try to print a ticket, all of the ticket metadata does
show up and occupies about a page before the body of the ticket is
printed.

The print stylesheet does need some updating for 4.0 and could use some
all around love to make it much more friendly, but that ticket metadata
was always meant to print. It’s basic information about the ticket that
people expect to see.

I see, so to make it take up less room on the page, collapse the
metadata sections. A complete mis-interpretation of how it was supposed
to work on my part, thank you for clarifying…

(The selectors you’re seeing are referencing chrome around the ticket
metadata, not the metadata itself.)

Thomas


2011 Training: http://bestpractical.com/services/training.html

Bob Miller
334-7117/660-5315
http://computerisms.ca
bob@computerisms.ca
Network, Internet, Server,
and Open Source Solutions

Hi all,

I’m having a problem that I’d like to see if anyone has experienced before. We are running RT 4.0.0 on RHEL 5, Mysql and Apache powered.

Many of our users are running IE 8 and 9. These users cannot print a ticket properly. The user receives a printout with the metadata section containing no headers, and the ticket history is completely whitespace. Then the printout include a superfluous page or several superfluous pages.

It’s also pertinent to note that RT tends to hang/crash IE when doing a print preview.

Steps to reproduce crash:

From Windows 7, IE9:

  1. Open RT 4.0.0, select ticket from home screen
  2. Hold down Alt -> Tools -> Print Preview
  3. Hit the “next” arrow to page through two or three screens
  4. IE hangs and must be restarted

Steps to reproduce odd printing:

  1. Open RT 4.0.0, select ticket from home screen
  2. Hold down Alt -> Tools -> Print
  3. Select printer, and view the results. I’ve scanned in a redacted ticket to illustrate.

This has been reproduced on 4 test machines thus far.

Thanks,

Dan

print_example_redacted.pdf (139 KB)

PGP.sig (275 Bytes)