379216 - Courier New and monospace rendered incorrectly when bold

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Joseph Mansfield]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3

Although the Courier new and monospace fonts are supposed to be monospaced, when you bold some text, the line-height is increased by 1px, therefore disrupting any monospacing.

Reproducible: Always

Steps to Reproduce:
1. Create a page with a passage of text in Courier New or monospace fonts
(Set the line-height too, if you want; the problem still occurs)
2. Highlight a couple of words on one of the lines with either a <b> or <strong> tag
3. When viewing the page, highlight the text and notice the increase of line-height where the bolded text is.
Actual Results:  
The line-height becomes 1px more than it should be.

Expected Results:  
The line-height should be the same as the rest of the text.

Comment 1

[Samuel Sidler (old account; do not CC)]

Attachment: Testcase from comment 0?

Is this testcase what you mean? If so, I don't see any problem using Firefox 2.0.0.3 on Windows XP SP2 or Mac OS X.

Comment 2

[Carsten Book [:Tomcat]]

also wfm on Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.4pre) Gecko/2007042503 BonEcho/2.0.0.4pre

Comment 3

[Tyler Downer [He/Him]]

This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode

Comment 4

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.