Open Bug 706221 Opened 13 years ago Updated 2 years ago

firefox doesn't support indic web fonts (using @font-face), on any Mac OS 10.x where font is not already installed on computer.

Categories

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

8 Branch
x86
macOS
defect

Tracking

()

UNCONFIRMED

People

(Reporter: guyvonh, Unassigned)

References

()

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/534.51.22 (KHTML, like Gecko) Version/5.1.1 Safari/534.51.22

Steps to reproduce:

I used font squirrel to generate an @font-face kit (supposedly "bullet-proof") for an Oriya font. http://worldwide.familyradio.org/test/test/ori1UniMedium-demo.html

I also tried a non-indic font under the same scenario. 


Actual results:

The font does not render on any version of firefox for any version of mac (so long as an Oriya font is not already installed on the mac). It does, however, render fine on other browsers and in firefox for windows (regardless of whether oriya font is installed on system). 

The non-indic, latin font worked fine. Therefore the problem appears to only affect unicode ranges outside of the basic latin range.


Expected results:

Firefox on mac should be able to render the indic font provided via @font-face, regardless of whether it is available on the user's OS.
Component: General → Layout: Text
QA Contact: general → layout.fonts-and-text
The issue here is that Firefox on OS X doesn't support fonts requiring OpenType Layout for Indic scripts, it only supports AAT fonts. This is because the Core Text framework on OS X didn't support Indic OpenType behavior, at least up through v10.6, and so the font would not render correctly. I think 10.7 may have introduced more capabilities in this area; if so, we should revise the font code in Gecko so that it accepts such fonts.
That is good information. That said, even using an AAT Oriya font, such as the Oriya MN (packaged with Lion), the same issue prevails. (see http://worldwide.familyradio.org/test/test4/OriyaMNRegular-demo.html )

The other thing to think about is that Safari on 10.6.7 even is able to display both the the AAT indic font (as well as the non-AAT one) just fine.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.