Created attachment 636122 [details] thunderbird_font_bug.png User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.56 Safari/536.5 Steps to reproduce: Note, this bug was non-existent in version 12. However versions 13 and 15 both have this bug. Using Linux for all. Send the following message to yourself using UTF-8 formatting. Note, ISO-8859-1 does not have this bug, only UTF-8: This is just text <!-- Displays correctly --> <p>Text in p here</p> <!-- Displays correctly --> <div>Text in div</p> <!-- Displays correctly --> <table> <tr> <td>Test in table cell (valid)</td> <!-- Does not display correctly --> </tr> </table> <tr>Test in invalid tr</tr> <!-- Displays correctly --> <br /> <td>Test in invalid td</td> <!-- Displays correctly --> <br /> <table>Test invalidly inside table</table> <!-- Displays correctly --> <table> <td>Test in td without tr</td> <!-- Does not display correctly --> </table> <table> <tr>Test in tr without td</tr> <!-- Displays correctly --> </table> <tr> <td>Test in td with tr without table</td> <!-- Displays correctly --> </tr> Actual results: Notice how the text that is within a <td> that has a parent (or grandparent) <table> is displayed using an incorrect (larger) font. However, if you reply to the message, it is rendered correctly in the reply window. Also, manually clicking on "View" > "Character Encoding" > "Western (ISO-8859-1)" fixes this problem immediately. Expected results: All fonts should be rendered the same no matter where they appear in the HTML or what encoding is used unless changed by CSS or similar.
Note: manually changing font.size.variable.x-unicode to the same value as font.size.variable.x-western seems to fix the problem. So then maybe the question should be why part of the email is rendered in unicode and the other part in western.
Can we have a test email ?
I already provided one (see my original comment), so all you have to do is send it with header "Content-type: text/html; charset=utf-8". I've added another attachment containing the email.
You need to log in before you can comment on or make changes to this bug.