Open Bug 527089 Opened 15 years ago Updated 2 years ago

Browser fails to correctly render text with CSS specifying the Hancock font

Categories

(Core :: Layout: Text and Fonts, defect)

1.9.1 Branch
x86
Windows XP
defect

Tracking

()

UNCONFIRMED

People

(Reporter: emartin, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4) Gecko/20091016 Firefox/3.5.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4) Gecko/20091016 Firefox/3.5.4

When viewing a file whose CSS specifies the use of the free-to-download Hancock font, that specification is ignored.

Reproducible: Always

Steps to Reproduce:
1. Create an HTML file with body containing only the following:
<div style="font-family:Hancock,Verdana;">Sample text.</div>
2. View in Firefox 3.5.4.
Actual Results:  
It will render in the Verdana font whether or not the Hancock font is installed on the viewing machine.

Expected Results:  
If the Hancock font is installed, it should render in the Hancock font.

When viewed in IE7, IE8, Opera, and Chrome it renders in the Hancock font. This misbehavior on Firefox is new. It definitely did not happen with Firefox 3.0, and I'm not aware of its having happened with Firefox 3.5.2 or 3.5.3. The problem appears to be limited to the Hancock font. If I replace "Hancock" by any other one-word name of a font installed on my computer, the file renders correctly in that font.
Component: General → Layout: Text
Product: Firefox → Core
QA Contact: general → layout.fonts-and-text
Version: unspecified → 1.9.1 Branch
Further testing shows that this remains a problem with Firefox 3.5.5 on

32-bit Windows XP SP3, 32-bit Windows Vista SP2, 32-bit Windows 7 RC2.

It is NOT a problem with Firefox 3.5.4 on 32-bit Ubuntu 9.10.
This remains a problem with Firefox 3.6 RC1 on 32-bit Windows XP SP3. I haven't checked on the other Windows OSs mentioned above because I don't have FF3.6RC1 installed on them.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.