Open Bug 435807 Opened 18 years ago Updated 4 years ago

Half-inch margins added to printouts.

Categories

(Core :: Printing: Output, defect)

x86
Linux
defect

Tracking

()

People

(Reporter: fantasai.bugs, Unassigned)

References

Details

Mozilla seems to have a hard-coded minimum page margin. I can't print "full-bleed" PDFs. Steps to Reproduce: 1. In Page Setup create a custom paper size with zero margins and select it. 2. Open Print Preview or print a web page using the Print to File option. Expected Results: Zero margins, i.e. the initial containing block should be the entire paper size. Actual Results: Mozilla puts ~1/2 inch margins between the paper edge and the content. Tested on Gecko/2008052221 Minefield/3.0pre in Linux.
Actually, the margin is *in addition* to the specified margins, and it is exactly half an inch.
Summary: Can't use zero (or small) margins to print PDF → Half-inch margins added to printouts.
Yup, this is known behavior -- the half-inch comes from the about:config pref: print.[printer_name].print_margin_XXX where XXX = top,right,bottom, left. This pref describes the offset from edge of printable area to edge of content. This is as distinct from the "unwriteable margin", which is what gets set by the Page-Setup dialog (*.print_unwriteable_margin_XXX). The unwriteable margin defines the offset from edge of paper to edge of printable area. (To complicate things further, there's one more pref -- print_edge_XXX -- which defines offset from edge of printable area to header / footer position) Sadly, we don't have a field in the Linux print-configuration dialogs for the print_margin_XXX or the print_edge_XXX prefs. I believe we have the same basic behavior on OS X (with the OS X print dialogs) so this isn't a linux-only issue. (Windows uses our old print-configuration dialogs, though, which give access to the print_margin and print_edge prefs. So, should not be a problem on Windows) Easy workaround = tweak the print_margin prefs by hand. :)
Version: unspecified → Trunk
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.