[dev] Re: [cvs] commit: horde/themes print.css

[Chuck Hagenbuch]

Quoting Jan Schneider <jan at horde.org>:

> But how well is @media print supported in browsers? And consequences does
> this change have?

Looks like it's pretty wide, certainly in the browsers that we work 
well in now:
http://www.codestyle.org/css/media/print-BrowserSummary.shtml

> It would probably mean that the print icon will go away, because it wouldn't
> do anything but opening the same view in a new window and potentially
> triggering the print dialog. That means that the user needs to click the
> browser's print icon, leading to confusion. If he wants to print only one
> frame (the common scenario) it leads to even more confusion, how many end
> users know how to properly print frames?

There would be no need to open a new window; the print button could stay and
trigger the browser's print dialog.

> Plus, using a generated print view shows the user how this page will look
> like being printed out. How many end users know of (browser builtin) print
> previews or use them before printing? In the end they would get something
> printed out that looks different from what they saw on the screen when they
> hit "Print". Confusion.

Then we could keep the new window and explicitly apply the print stylesheet to
it, so they see on the screen what prints out.

> While using different media types for CSS has its merits, especially for
> static pages, I don't think it can outperform server generated print views,
> especially if the pages are server generated anyway.

The point is that this is a much, much simpler way to make things print out
well, without mucking with all of our code.

-chuck

-- 
"But she goes not abroad in search of monsters to destroy." - John 
Quincy Adams