[Webkit-unassigned] [Bug 70153] New: Display conflict involving imported @fontface fonts and locally available fonts

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Oct 14 15:25:48 PDT 2011


           Summary: Display conflict involving imported @fontface fonts
                    and locally available fonts
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Macintosh Intel
        OS/Version: Mac OS X 10.7
            Status: UNCONFIRMED
          Severity: Major
          Priority: P2
         Component: CSS
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: matt.scheurich at gmail.com

Created an attachment (id=111096)
 --> (https://bugs.webkit.org/attachment.cgi?id=111096&action=review)
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.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list