Bug 70153 – Display conflict involving imported @fontface fonts and locally available fonts

• Component: Text
• Status: RESOLVED INVALID

[Matt S]

Created attachment 111096 [details]
Showing the conflict between an imported @fontface font when it is also available locally

I've found on sites that utilise the Google Webfonts service that if I already have the font installed on my computer (Google Webfonts allows you to download the files to use in designs), when displayed on a website with an @fontface call to a font with the same name that is locally available, each character in the font is rendered with a strange character which makes text unreadable.

This has happened in both latest versions of Safari and Chrome on Mac OS X.7 so I presume it is a Webkit issue (Firefox has no such issue).

To recreate, simply download a font from the Google Webfonts page (I'd suggest Open Sans as its quite common), install it in your Font Book or other such font management program and then view the main Google Webfonts page.

A workaround I've figured out is to import the font under a different @fontface name, which is a bit annoying as I'd prefer to not download the font if it is already available on the viewer's computer.

Is anything logged to the system console when this first happens? You can use the Console application to monitor the system console.

[Matt S]

System.log displays these errors when viewing www.google.com/webfonts

Oct 16 13:26:50 armitage sandboxd[73334] ([73289]): WebProcess(73289) deny file-read-data /Users/matts/FontExplorer X/Font Library/O/Open Sans Bold/OpenSans-Bold.ttf
Oct 16 13:26:50: --- last message repeated 7 times ---
Oct 16 13:26:50 armitage sandboxd[73334] ([73289]): WebProcess(73289) deny file-read-data /Users/matts/FontExplorer X/Font Library/O/Open Sans/OpenSans-Regular.ttf
Oct 16 13:26:50: --- last message repeated 7 times ---
Oct 16 13:26:50 armitage sandboxd[73334] ([73289]): WebProcess(73289) deny file-read-data /Users/matts/FontExplorer X/Font Library/O/Open Sans Bold/OpenSans-Bold.ttf
Oct 16 13:26:50: --- last message repeated 3 times ---
Oct 16 13:26:50 armitage sandboxd[73334] ([73289]): WebProcess(73289) deny file-read-data /Users/matts/FontExplorer X/Font Library/O/Open Sans Extrabold/OpenSans-ExtraBold.ttf
Oct 16 13:26:50: --- last message repeated 7 times ---
Oct 16 13:26:50 armitage sandboxd[73334] ([73289]): WebProcess(73289) deny file-read-data /Users/matts/FontExplorer X/Font Library/O/Open Sans Semibold/OpenSans-Semibold.ttf
Oct 16 13:26:50: --- last message repeated 7 times ---
Oct 16 13:26:50 armitage sandboxd[73334] ([73289]): WebProcess(73289) deny file-read-data /Users/matts/FontExplorer X/Font Library/O/Open Sans/OpenSans-Regular.ttf
Oct 16 13:26:52: --- last message repeated 3 times ---

Thank you!

Which version of OS X Lion are you using (You can find the version number in About This Mac)? Are you using font management software (such as FontExplorer X)?

[Matt S]

I'm using Mac OS X v10.7.1
I'm also using FontExplorer X Pro v2.5 (Build 4200) to manage my fonts.
The version of Safari is v5.1 (7534.48.3) and Google Chrome is v14.0.835.202

An issue affecting the display of fonts managed by certain third-party font managers in Safari has been fixed in OS X 10.7.2. Please try again with 10.7.2 or later.

[Matt S]

Hoo rah, it works!

Thanks for testing. I am going to close this as “invalid” because the fix was not in WebKit but in OS X.