-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dave Howorth wrote:
Randall R Schulz wrote:
I am almost always frustrated by the results of printing HTML pages from Firefox (I'm using version 2.0.x).
Interesting responses from various people and I agree with much of what's been said but I think everybody's missed the point ...
The most common problem I encounter is that text lines mean nothing to the pagination process and it is common for a row of text to be sliced horizontally and split across a page boundary.
This isn't true for Firefox, at least not for FF 1.5 or 2. Firefox does split text in complete rows as you'd hope (and it tries to follow most of CSS2). I never see the problem you describe with either FF1.5 or FF2.
I think it's much more likely that this is a problem with page margin or header settings or printable area in the Firefox or printer config. Sorry, I don't have any more specific suggestion to offer.
FWIW, the main problems I see with FF are:
- when authors use position:absolute wrongly (they haven't read CSS2 chap 13 - paged media as Per suggested :) and that leads to all the output just flowing off the bottom of a single page.
- when there's a long pre-formatted line, leading FF to shrink it to fit and making all the text unreadably small. I think FF is at least partly at fault for that.
Cheers, Dave
Hmmm.. In many cases this is not FF but sloppy Web Authoring as already been pointed out elsewhere but.... Firefox 2.x was ok for me for quite a while on 10.2, but after a particular point it started getting very confused about paper size and orientation. (landscape became portrait and vice versa, and A4 seemed to be coming out as either A5 or letter and page top right was somewhat randomly positioned). The only way I could get anything remotely useful out of it was to go into landscape at 50% and then one usually needed a microscope to read the results :-). So if I needed to print a page from a browser (which is rare) I got into the habit of accessing the page via Konqueror and printing which usually worked OK. As I printed rarely from a browser I had no way of effectively pinning down which combination of updates/configuration changes was responsible for the change in behaviour (and to be honest I was not prepared to invest the time I because I could work around it, FF was the only application that was effected, and web searching did not turn up any clues about where to start looking for a solution). Since upgrading 11.0 and starting using v3 the problem has gone away (for the moment). - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkitWqcACgkQasN0sSnLmgJK9QCgq5DFOBDpINtgZyAf2+J82G6h T7YAniuK36AvGTa5uB3EO1IP8UKD7N1f =SWzz -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org