329671 - italic text renders illegibly on MacOS X

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Christopher Mason]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

The <em> tag renders poorly on Firefox 1.5.0.1 on MacOS X (10.4.5).  The font is poor and text is clipped.  It almost appears as if the text is being italicized twice.  This doesn't occur on Windows XP.

Reproducible: Always

Steps to Reproduce:
See attached HTML fragment.
Actual Results:  
See attached mac1.0.5.1.png.

Expected Results:  
See attached win1.0.5.01.png.

Comment 1

[Christopher Mason]

Attachment: HTML fragment containing <em> tag and sans-serif font.

Comment 2

[Christopher Mason]

Attachment: Screenshot of <em> tag and sans-serif font rendered incorrectly on Mac.

Comment 3

[Christopher Mason]

Attachment: Screenshot of <em> tag and sans-serif font rendered correctly on Windows.

Comment 4

[Christopher Mason]

Note that sans-serif font is also necessary for this to be reproduced.  Serif font does not show this bug.

Comment 5

[Jesse Ruderman]

WFM with the testcase in comment 1 and the w3.org URL.  I'm using today's Firefox trunk build on Mac OS X 10.4.5 on a PowerBook.

Comment 6

[Christopher Mason]

Attachment: Screenshot of <em> tag and sans-serif font rendered incorrectly on Mac build 20060307.

Comment 7

[Christopher Mason]

Note that <i> shows the same behavior.  Changing subject to reflect this.  This is with trunk build 20060307.

Comment 8

[Christopher Mason]

Further digging shows this to be a problem with two postscript fonts (Courier and Helvetica) that were installed on my system.  Oddly, the fonts themselves are fine; there must have been some caching happening somewhere because after removing and reinstalling them, they render fine.  Not sure why only Firefox was tickling this and why only at certain sizes.  I doubt anyone else will have this problem, so I'm going to close the bug.  Frustrating waste of time...