Open Bug 256625 Opened 20 years ago Updated 2 years ago

page setup options for header and footer lines not consistent with those in about:config


(Core :: Printing: Setup, defect)





(Reporter: fuglv, Unassigned)


(Blocks 1 open bug)


User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040719 Firefox/0.9.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040719 Firefox/0.9.1

There are two places to configure what headers and footers will be printed with
a page:
in File->Page Setup

The latter doesn't have any effect, only the former does.
Further experimenting revealed that print.print_{...} apparently isn't used at
all. File->Page Setup will create override options
print.print_<curent_printer>_{...} that have at least one-way propogation (Page
Setup to about:config)

It boils down to this, the configuration in about:config has no effect. To
configure headers/footers you have to do it in Page Setup, which will create
override options for a specific printer, which can then be seen and modified in
about:config. The regular options seen in about:config should be the ones
modified and used and printer-specific overrides should only be created and used
in an explicit manner.

Reproducible: Always
Steps to Reproduce:
1.goto about:config
2.filter on header
3.change print.print_{header,footer}*

1.goto File->Page Setup
2.configure headers/footers
3.printer-specific options appear in about:config
Actual Results:  
printed page still has default headers and footers

page prints as configured, but "global" options are overriden

"global" (print.print_{header,footer}*) options have no effect

Expected Results:  
changing the header/footer options should apply to all printers, and
printer-specific overrides should be explicit if even existent.
Confirmed using Mozilla 1.8a4 on Windows XP SP1.
Assignee: firefox → prefs
OS: Linux → All
Product: Firefox → Browser
QA Contact: mconnor
Version: unspecified → Trunk
Ever confirmed: true
Product: Browser → Seamonkey
(Filter "spam" on 'prefs-nobody-20080612'.)
Assignee: prefs → nobody
QA Contact: prefs
This is a big issue for corporate deployments.

You can't use the CCK (or any mechanism) to preset the print values because they are specific to the name of the printer.

Firefox should use the default values if none have been set explicitly in Page Setup.

(and if the default values aren't used, why are they in all.js)
Severity: minor → normal
Component: Preferences → Printing: Setup
Product: SeaMonkey → Core
QA Contact: preferences → printing.setup
I see the same problem with Firefox 13.0.1 (on Fedora 17).
js-print-setup(1) provides (at least partial) workaround to this bug.

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.