On 4 Oct 2007, at 21:08, Alan K. Gay wrote: > I have found that, while both the IE and FF print engines can be > buggy and > produce different results than the screen, the FF engine is by far the > worst, and quite unpredictable. It's been a year or so since I've > had to > regression-test printing in FF, but I would suggest starting by > taking all > the positional stuff out of your css (floats, absolutes, etc) and > then add > it back incrementally so you can see where things are breaking > down. Once > you find the gremlin(s), you can use the @media function to feed > different > CSS to the print engine vs the display. You may also need to make the > print-only css different for IE and FF, so you will need to us the IE > conditional style sheet approach. >
Many thanks Alan for your good advice. It was the float instruction for the navigation div which was the problem. I had tried to write a print style-sheet originally, but ran out of time before I could make it work properly. I've now done it and it seems to work OK with all the browsers I've used in both OS X and Windows XP. The name and first address fields on the Join the Association page (www.local- history.co.uk/nlha/join.html) do come out a little longer than the other address fields in some browsers, but I can live with that. Once again, many thanks. Susan Griffiths ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
