Firefox is a web browser, printing is not a major concern.
When I want to print content, I copy/paste it into a word processor. You
will get much more access into how the page is printed then any browser
wil give you.
Lee
--
Leonidas Jones, Mozilla/Netscape Champion
Learn about the Champs! http://mozillachampions.ufaq.org
The UFAQ'S http://www.ufaq.org/
http://www.mozilla.org/community/etiquette.html
http://mozilla.com http://mozilla.org
I disagree. HTML (when properly written) can adapt to various page
dimensions, etc. very nicely. I print directly from the browser
quite often. I also find the utility Fineprint very useful
(<http://www.fineprint.com>) to combine multiple pages into a
single printable document, especially in booklet form.
--
Chuck F (cbfalconer at maineline dot net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home.att.net>
> Leonidas Jones wrote:
<snip />
>> When I want to print content, I copy/paste it into a word processor.
>> You will get much more access into how the page is printed then any
>> browser wil give you.
>
> I disagree. HTML (when properly written) can adapt to various page
> dimensions, etc. very nicely.
In fact, with CSS, you can set an @print stylesheet, set page breaks, &c,
but Lee's point is well taken, since HTML tends to be written for the
viewport rather than for the printed page. . . .
/b.
<snip />
--
'There is caution, and there is irrational paranoia.' -- Ron Hunter
--
Ron Hunter rphu...@charter.net
CAN be, yes, but lazy HTML coders often don't give any consideration to
this issue.
--
Ron Hunter rphu...@charter.net
Just to add my $.02, it seems, to me at least, that where FF printing
breaks down is with tables, or pages laid out with tables.
Pages with just basic formatting, or using CSS for formatting, without
complicated tables, seem to print just fine for me. Even simple tables
can be a problem, in certain cases.
I believe that this issue is being addressed by the 'reflow rework' for
FF3. See, for example, my post in this thread:
http://groups.google.com/group/mozilla.support.firefox/browse_frm/thread/8d05e539e6399c16/30f4dd71cfda7c2a
--
Alex K.
If you are not making the pages, you might try copying and pasting them
into a word processing program, which is more capable of this sort of thing.
I may be wrong, but I thought the reflow work was been focussed on Acid2?
(See, /e.g./, <http://en.wikipedia.org/wiki/Acid2>.)
/b.
That could be. I made my assumption based on researching several print
layout bugs on bugzilla, that pointed back to the reflow rework bug.
Unfortunately, I didn't bookmark the bugs in question, so I don't have
specifics.
--
Alex K.
Umm yeh, learn CSS2.
Don't mean to be rude but what would you know sister.
You're obviously from the bad old days of Netscape when tags were used
for formatting.
Good call.
<caption></caption> tags are only for tables my friend.
Why what? Why the browsers don't support the CSS page break properties
very well: I don't know, I can only assume that this has not been a
priority for the browser makers. Or do you mean why a word processing
program is better? Just look at, for example, the various Insert Page
Break commands that Word offers: you have tremendous control over
pagination, page breaks, etc.
Garth alert, resident troll. Ignore his posts.