246383 - The contents of form element like select lists and text boxes are printed in a much larger font than that of the surrounding page contents.

Status: RESOLVED EXPIRED

(Core :: Printing: Output, defect)

Description

[Buz Dreyer]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040608
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040608

We are printing to an HP LaserJet 4000N printer and an HP DeskJet 970C from our
Mac G4 workstations.  The problem occurs on both printers.



Reproducible: Always
Steps to Reproduce:
1. Select PRINT... from the FILE menu.
2. Click the Print button.
3.

Actual Results:  
The contents of the form fields (select lists, text boxes, etc.) were displayed 
in a font size much larger than the surrounding page contents.  The font size is
much larger than that displayed on the screen.

The printed image looks clunky.  It does not help our web page development
efforts when discussing new designs.

Expected Results:  
The font size of the form elements should be similar to that displayed on the
screen.

Is there some CSS technique that can control this problem?

Comment 1

[Buz Dreyer]

This is a new behavior that did not occur in earlier versions of Mozilla.  If it
is not remedied soon, we may have to stop recommending Mozilla's use to our
departmental users.

Comment 2

[Greg K.]

Buz, does the problem still occur if you remove your linked CSS from that document?

Comment 3

[Jesiah S]

You can tell the browser to use a diffrent css file for printing and tell it to
use smaller font size when printing.  You can do this by adding media="print" to
the <LINK> tag or add @media print {} in a css file.
If you can make a small testcase that shows this problem that would be great.
FWIW I don't see this in LInux 2004072607

Comment 4

[David Aznar Reguero]

Using Debian's unstable mozilla-browser_1.7.5-1 without xprint I don't get
what's inside of "readonly disabled" "input" boxes.
Could you verify?
Is my problem related to this bug? or should I open another bug report?

I also can't verify the original bug report.

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.