498595 - @font-face rendering as hex boxes

Status: RESOLVED DUPLICATE of bug 489445

(Firefox :: General, defect)

Description

[Nick]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b4pre) Gecko/20090401 Ubuntu/9.04 (jaunty) Shiretoko/3.5b4pre
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b4pre) Gecko/20090401 Ubuntu/9.04 (jaunty) Shiretoko/3.5b4pre

The use of @font-face on the Jetpack website to load a truetype font is rendering for me as boxes with hex in. Removing the font-face declarations (or the font-family of DroidSans) fixes it.

This site also has the same problem for all fonts:
http://opentype.info/demo/webfontdemo.html


Reproducible: Always

Steps to Reproduce:
1. Visit the Jetpack site or the other linked site.
Actual Results:  
Characters are displayed as boxes with their hex value inside. (I'll see if I can attach a screenshot after submitting this.)

Expected Results:  
The actual characters should be displayed (ideally using the provided font-face)

Comment 1

[Nick]

Attachment: Screenshot of Jetpack site

Comment 2

[Nick]

Attachment: Screenshot of opentype.info page

Comment 3

[Nick]

Comments on this blog post show a couple of other people with the same problem... just to confirm that it's not my crazy computer.

https://labs.mozilla.com/2009/05/introducing-jetpack-call-for-participation/

Comment 4

[Benjamin Esham]

Attachment: Screenshot of the bug showing up on http://senate.alfred.edu

I can confirm this on Ubuntu when visiting e.g. <http://senate.alfred.edu>.

User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b4pre) Gecko/20090401 Ubuntu/9.04 (jaunty) Shiretoko/3.5b4pre

uname -srvm: Linux 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686

Comment 5

[Benjamin Esham]

I should add that I do *not* see this behavior with Firefox 3.5b99 under the latest version of Mac OS X.

Comment 6

[philippe (part-time)]

Try with the latest Shiretoko nightly:
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-1.9.1/

This is almost certainly bug 489445.

Comment 7

[Nick]

Yes, it renders fine for me now so it's almost certainly the same thing. I'll remember to try the latest version next time. Thanks!