Email signatures default to browser font, not mail composition font

NEW
Unassigned

Status

MailNews Core
Composition
--
minor
15 years ago
9 years ago

People

(Reporter: Jim Booth, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.4b) Gecko/20030422
Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.4b) Gecko/20030422

Signatures (and other supplied text) in HTML email messages use the font
specified in 
Edit / Preferences / Appearance / Fonts, 
not the font in 
Edit / Preferences / Mail & Newsgroups / Composition

Also affected: the text added to replies by composer, for example:
user@isp.com wrote: 

Reproducible: Always

Steps to Reproduce:
1. Set different fonts in the two preferences above (i.e. Appearance / Fonts /
Proportional to Serif, and Mail / Composition to Arial) 
2. Compose a new email message

Actual Results:  
Signature is in one font (the browser default), and message text in another
(mail default).

Expected Results:  
Signature should default to the mail default font.

Another possibility would be to allow a setting for signature and other elements
separately, such as by using an HTML signature file or a CSS style setting
somewhere.
Unless you specify a specific font for your signature when you create it, signature text is simply 
displayed in whatever is the "Variable Width" font.    Same goes for reply/forward text... in HTML it's 
just "Variable Width" -- no font applied.

Comment 2

13 years ago
(In reply to comment #1)
> Unless you specify a specific font for your signature when you create it,
> signature text is simply displayed in whatever is the "Variable Width" font.   

Not necessarily: a plain-text sig is placed in a <pre> tag and so is shown in 
the Monospace font -- and there's no way to change that behavior, other than 
switching to an HTML sig.


> Same goes for reply/forward text... in HTML it's 
> just "Variable Width" -- no font applied.

True enough.  The only one with a simple workaround is the HTML sig, which can 
specify its own font.

Comment 3

13 years ago
*** Bug 271253 has been marked as a duplicate of this bug. ***
Product: MailNews → Core

Comment 4

13 years ago
Is this a
- viewer bug (sent msg source is fine, no hint why it differs)
- Composer bug (bug already visible during composition.
  Only there, not in viewer?)
- sending bug (fine in Composer, bad in msg source, bad in viewer)
?

Might be caused by bug 278260?

Comment 5

13 years ago
(In reply to comment #4)
> Is this a
> - viewer bug (sent msg source is fine, no hint why it differs)
> - Composer bug (bug already visible during composition.
>   Only there, not in viewer?)
> - sending bug (fine in Composer, bad in msg source, bad in viewer)
> ?

It's a plain ol' composition bug.  Any pre-entered text in a new composition is 
not enclosed within the <font></font> tags.  The *real* problem is that 
composition uses <font> rather than a style sheet.


> Might be caused by bug 278260?

Not at all.

Comment 6

13 years ago
*** Bug 261579 has been marked as a duplicate of this bug. ***

Comment 7

13 years ago
*** Bug 295249 has been marked as a duplicate of this bug. ***

Updated

9 years ago
Assignee: ducarroz → nobody
QA Contact: esther → composition
(Assignee)

Updated

9 years ago
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.