Open
Bug 212369
Opened 21 years ago
Updated 2 years ago
Headers/Footers ignore page margins
Categories
(Core :: Printing: Setup, defect)
Tracking
()
NEW
People
(Reporter: bmoz.6p1, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.4b) Gecko/20030607 Mozilla Firebird/0.6 Build Identifier: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.4b) Gecko/20030607 Mozilla Firebird/0.6 When printing a page the header/footers are set to the extreme edges of the page and are often partialy cut of by the hardware margins. Increasing the page margins in the page setup dialog effects all the printed material except the header/footer. When setting the side margins to an inch for example the user expects al the printing to move within these margins including the header/footers, but they are the only element that does not move. This may be related to bug# 130075 were they appear to be expierencing trouble with the header/footers running off the top and botto of the page. Reproducible: Always Steps to Reproduce: 1.Firebird's default settings work to reproduce this. 2.print a web page 3.observe that the header/footers do not adhear to the 1/2 in. left and right margins set for us-letter, and that some of the letters at the extreme left and right may be cut off depending on the hardware capabilities of your printer. 4.change the left margin from it's default of 1/2 in. to 1 and 1/2 in. and print the same page again. 5.observe that all the content of the page, but the header/footers, has shifted 1 in. further to the right, leaving the header/footers untouched. Expected Results: The expected results is for the header/footers to obey the margin settings, along with the content of the page, atleast in respect to the side margins. Some apps allow setting special margin areas, top/bottom, for the header/footers but the left/right are honored. Abiword for example.
Updated•21 years ago
|
QA Contact: asa
Comment 2•21 years ago
|
||
*** Bug 228214 has been marked as a duplicate of this bug. ***
Comment 3•21 years ago
|
||
Confirming. Other people are seeing this (see dupe).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 4•20 years ago
|
||
I can confirm this as well. I've fiddled with several of the settings in about:config, and couldn't find anything that resolved this issue. Have any of you tried manipulating about:config settings directly to see if anything there makes a difference (to see if I missed something, or if there's something that works for you that doesn't for me.)
As a company pushing OS software, we try to push Firefox as the browser of choice. We wrote some web based medical software but are having difficulty with the print margins. In order for the forms to come out right, the margins have to all be set = to 0. All of the headers and footers to --blank-- Reproducing the error... Open the browser and click into a report, click file->print the output is messed up. Overlapping the page, and headers and footers get printed. Click file->page setup even though the margins are already at 0 and headers and footers are already blank, you have to press ok. Now click file->print and it prints fine. The bug: Mozilla disregards or ignors page setup settings when printing until file->pagesetup->ok are clicked ever time a the browser opens. Even if it is a new or child window, you have to click file->page setup->ok just to enforce the margins and headers and footers. This is driving us, our clients and me nuts. Any thoughts? https://bugzilla.mozilla.org/show_bug.cgi?id=130075 Quote: Maybe this bug needs to go elsewhere, like to the ghostscript people. It's a very longstanding bug (several years!) and I've come on fixes for it posted to the geocrawler archives from the late 90s. https://bugzilla.mozilla.org/show_bug.cgi?id=212369 Is anybody going to fix this bug? Printing is a big thing, and it is a very old bug!
Updated•19 years ago
|
Assignee: firefox → nobody
QA Contact: bugzilla → general
Updated•11 years ago
|
Component: General → Printing: Setup
Product: Firefox → Core
Depends on: 1250674
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•