print.print_(header/footer)(position) doesn't accept literal string on Mac OS X

NEW
Unassigned

Status

()

--
minor
10 years ago
6 years ago

People

(Reporter: sebastien.bacon, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk
PowerPC
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; fr; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5
Build Identifier: Version 2.0.0.19 (20081209)

I try to write my name on top left of printed mail.
I edit the print.print_headerleft so that it reads "Bacon Sebastien"

On Windows Vista it's OK (same built version oh TB).

On Mac OS X, nothing is printed in the corner.
I tried with another string, quoted string, double-quoted string, I even replaced text in the prefs.js, but nothing is written. I tried mixed &T&D or &T - &D : doesn't work as well. it seems like, on Mac OSX, only single values &U,&D,&T and &PT are accepted.

Reproducible: Always

Steps to Reproduce:
1. change the print.print_headerleft from "&T" to "this is a test"
2. print a mail
Actual Results:  
nothing is printed on the top left corner

Expected Results:  
"this is a test" should be printed
(Reporter)

Comment 1

10 years ago
I just have the same problem with ThunderBird 3 Beta 1
Version: unspecified → 2.0
based on http://mxr.mozilla.org/comm-central/search?find=%2F&string=print_headerleft this looks like a Core bug.
Component: Preferences → Printing: Setup
Product: Thunderbird → Core
QA Contact: preferences → printing.setup
Version: 2.0 → Trunk
Duplicate of this bug: 376653
Confirming based on tests done by a user on support.mozilla.com (chat u50m491072820).  (Headers and footers are ignored when changed to a non-default string)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Blocks: 505414

Comment 5

7 years ago
This issue persists with both Firefox 3.6.21 and 6.0.2 on Mac OSX. In addition to nothing being printed where a custom header/footer was defined, the config value is actually clobbered as soon as the print dialog is brought up. Not sure if this makes the fix any easier, but I would suggest looking first to see if it is the print dialog that is changing the config values as that may be the only issue.
You need to log in before you can comment on or make changes to this bug.