Closed Bug 414189 Opened 18 years ago Closed 15 years ago

Checkboxes/radio buttons become too small to be readable when printing a page

Categories

(Core :: Printing: Output, defect)

1.9.0 Branch
x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: david, Unassigned)

Details

(Whiteboard: [closeme 2011-03-15])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b2) Gecko/2007121120 Firefox/3.0b2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b2) Gecko/2007121120 Firefox/3.0b2 When printing a page that contains checkboxes and/or radio buttons, they print out too small to be readable or provide any printout that can be representative of a form. This can be seen by both print previewing and actually printing the page. Reproducible: Always Steps to Reproduce: 1. Go to the bugzilla new bug reporting page (https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&format=guided) 2. Print the page or do a print preview Actual Results: Checkbox next to "This is a security problem that should be kept confidential until addressed (see the mozilla.org security policy for more details)." is incredibly small. Expected Results: Checkbox should be the same size it is on screen or simply a normal size that is clearly readable. This should also be the case when zoomed out or after selecting shrink to fit. If people fill out things like order forms that needed to be printed to be sent in, any data that is contained by checkboxes or radio buttons is probably useless because of their size when printed.
Also, just to note, this bug does NOT occur in Firefox 2. Firefox 3B2 (maybe B1 also, can't test it)
Component: General → Printing: Output
Product: Firefox → Core
QA Contact: general → printing
Version: unspecified → 1.9.0 Branch
do you see this issue still with version 3.6 or 4.0 beta?
Whiteboard: [closeme 2011-03-15]
No response to needed information. -> incomplete report
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.