Printable format broken

[Arancaytar]

This is my site: http://arancaytar.ermarian.net/

I am using this stylesheet to generate a printable version of the page
(using media="print"):

http://arancaytar.ermarian.net/sites/all/themes/itheme/print.css

But for some reason, Firefox will only print a single A4 page. Rather
than breaking the page once it is full, the entire content <div>
appears to stretch out of sight beyond the bottom margin of the page.

Curiously, the pagination works in IE7 - although that browser has
issues with the rest of the markup (such as wrapping <div>s that are
inside paragraph tags in <object>).

I am guessing that the error is in a stylesheet (if not in print.css,
perhaps in the other stylesheets on the page) - perhaps something to
do with "overflow"? But I can't figure out more than that...

[Jim Moe]

Re: Printable format broken

Arancaytar wrote:

This is my site: http://arancaytar.ermarian.net/
>
I am using this stylesheet to generate a printable version of the page
(using media="print"):
>

ISTR that you must add this to your print CSS file to be sure all
browsers get it:

@media print {

/* the print.css */

}

--
jmm (hyphen) list (at) sohnen-moe (dot) com
(Remove .AXSPAMGN for email)

[Arancaytar]

Re: Printable format broken

On Jun 6, 9:19 pm, Jim Moe <jmm-list.AXSPA...@s ohnen-moe.comwrote:

ISTR that you must add this to your print CSS file to be sure all
browsers get it:

The print.css file itself is used correctly by all browsers I tested
with (Firefox and Internet Explorer). It hides the sidebar and
navigation links, but shows the URL of hyperlinks behind the link
text. That doesn't seem to be the problem.

However, the content overflows over the edge of the first page without
starting a new page in Firefox. I've taken the time to make the markup
and CSS valid again, but the problem is still there...

--
Aran

[Arancaytar]

Re: Printable format broken

Okay, it seems to be caused by the "overflow:hidde n" property (makes
sense in a way). I don't know why the author of the original template
put that in, but then they didn't appear to hold with W3C validation
either. It works both in the normal form and in print now.


--
Aran