Allie Emigh-Carr wrote:
>It's working better now, but not perfectly. Seems to be fine in IE, but in Mozilla, it's not
recognizing when the page ends, so the text doesn't split between pages correctly. What I did to
fix the initial problem was to change the content position to relative instead of absolute. Again,
it made it better, but not perfect. Any suggestions?
>The pages with problems:
Well, it's position: relative that's causing the problem now. What
position: relative does is calculate where the element should normally
sit, leaving room for all other content, *then* it shifts it in the
direction you've told it. What this means is that you'll be left with a
gap where it would have originally sat had it remained in the normal flow.
You are shifting #content down by 127px, which means every page that you
print has a 127px gap at the top and 127px overlap at the bottom. This
is why the text is running off the pages in Mozilla.
I'd get rid of all positioning from #top and #content and just let those
two elements flow naturally. Then, give #content a left margin big
enough to "hold" #menu, and the only thing that needs to be positioned
is #menu (just like you currently have it).
In general, if you don't have to position something, don't. As you can
see, it often introduces unwanted quirkiness in other areas. You can
get rid of a lot of the positioning and still have things look exactly
the same as they do now.
You may also want to follow whoever it was on the thread who suggested
you get rid of the #menu on print -- it serves no purpose on paper, only
wastes space and ink. Let us know if you need info on setting up a
print style sheet.
Zoe M. Gillenwater
Highway Safety Research Center
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/