Open Bug 810814 Opened 11 years ago Updated 6 months ago

HTML font preferences do not apply to quote header

Categories

(Thunderbird :: Message Compose Window, defect)

Product:
Thunderbird
Component:
Message Compose Window
Version:
16 Branch
Platform:
x86
Windows XP
Type:
defect

Tracking

(Not tracked)

Status:
REOPENED

People

(Reporter: snoopy, Unassigned)

Details

Attachments

(1 obsolete file) 

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0.1
Build ID: 20120713134347

Steps to reproduce:

Enabled HTML composition by default, and chose "Helvetica/Arial" as default font. Quote format is "below message".
Hit "reply" to any message.


Actual results:

The default text before quote (On xxxx, user wrote:) does not follow font preference.

Sample source:

<html>
  <head>
    <meta content="text/html; charset=windows-1257"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix"><font face="Helvetica, Arial,
        sans-serif">123</font><br>

      On 2012.10.29 11:30, <a class="moz-txt-link-abbreviated" href="mailto:bellsouth_unblock@abuse-att.net">bellsouth_unblock@abuse-att.net</a> wrote:<br>
    </div>
    <blockquote ....


Expected results:

The <font> tag should end after the reply header text, or something similar. Now that text hasn't got any font specified. The current situation leads to mixed fonts in email clients, which have default display font set to other than Arial. 

Same behaviour in v12.
This is similar to https://bugzilla.mozilla.org/show_bug.cgi?id=203810, but that case focuses on font inconsistency during deletion. If the default font would be applied to reply header too, it won't happen at all.
Assignee: nobody → standard8

Patch had the wrong bug number. Correct would be bug 810815.

Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: FIXED → ---
Assignee: standard8 → nobody
Blocks: 1660603
No longer blocks: 1660603
Regressions: 1690467
No longer regressions: 1690467
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.