898152 - Seamonkey ignores print header and footer settings

Status: RESOLVED WORKSFORME

(SeaMonkey :: Preferences, defect)

Description

[Leo Heska]

Attachment: prefs.js with slight edits; substituted "DUMMY" in a few places

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Firefox/22.0 SeaMonkey/2.19 (Beta/Release)
Build ID: 20130630011339

Steps to reproduce:

Set print settings (File/Page Setup/Margins & Header/Footer) to blank.

Checked about:config and verified that all the following exist, are of type string, and the contents of each of them is blank:

   print.print_footercenter
   print.print_footerleft
   print.print_footerright
   printer_Canon_Pixma_MX410.print_footercenter
   printer_Canon_Pixma_MX410.print_footerleft
   printer_Canon_Pixma_MX410.print_footerright
   printer_Epson_WorkForce_635_Wireless.print_footercenter
   printer_Epson_WorkForce_635_Wireless.print_footerleft
   printer_Epson_WorkForce_635_Wireless.print_footerright
   printer_PDFCreator.print_footercenter
   printer_PDFCreator.print_footerleft
   printer_PDFCreator.print_footerright

File/Print Preview




Actual results:

Right header and footer, left header and footer, all show up. If I actually print, they actually show up on the paper.

In other words SeaMonkey is ignoring my print header and footer preferences.




Expected results:

Neither headers nor footers should have appeared.

Comment 1

[Phoenix]

You have
user_pref("print.use_global_printsettings", false);
in your prefs.js, is it intended to be there? Without it I have no problems with Header/Footer disabling.

Comment 2

[Leo Heska]

(In reply to Phoenix from comment #1)
> You have
> user_pref("print.use_global_printsettings", false);
> in your prefs.js, is it intended to be there? Without it I have no problems
> with Header/Footer disabling.

Thanks, Phoenix.

Commenting out that line appears to have fixed the problem. I don't know if it will cause any side effects; I haven't been able to see just what that setting is supposed to do. From the name of it, it seems like it would cause all printers to ignore their custom settings and use global ones. I haven't checked this yet.

The original problem is fixed.