Bug 7709 - WebKit only uses PostScript font names for CSS fonts
Summary: WebKit only uses PostScript font names for CSS fonts
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Text (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P3 Minor
Assignee: Nobody
URL: http://blog.wilsonet.com/archives/200...
Depends on:
Reported: 2006-03-10 16:13 PST by Daniel J. Wilson
Modified: 2022-06-24 21:02 PDT (History)
8 users (show)

See Also:

test case (770 bytes, text/html)
2006-05-03 05:23 PDT, Alexey Proskuryakov
no flags Details
All browsers differ (1.22 MB, image/png)
2022-06-24 09:26 PDT, Ahmad Saleem
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel J. Wilson 2006-03-10 16:13:07 PST
When specified in a stylesheet, 'Futura Condensed' is rendered as Futura in WebKit (build 13244). Both Firefox ( and Opera (9.0 preview) display the proper face.
Comment 1 Alexey Proskuryakov 2006-05-03 05:23:40 PDT
Created attachment 8092 [details]
test case
Comment 2 Alexey Proskuryakov 2006-05-03 05:40:31 PDT
Basically, WebKit appears to use PostScript font names, while Firefox uses Quickdraw ones.

I am not sure what the expected behavior is. CSS2 and CSS3 seem to use "font" and "font family" interchangeably, which is kind of weird IMHO. "Futura Condensed" and "Futura Medium" are font names, but not font family names (or at least I'm accustomed to the same terminology that Font Book uses).
Comment 3 Nicholas Shanks 2006-06-10 10:08:38 PDT
Yeah, you shouldn't be specifying "font-family: Futura Condensed", though <font face="Futura Condensed"> is fine. The fact that WebKit allows one to specify PostScript names such as Futura-Condensed is an undocumented feature ;-)
Comment 4 Alexey Proskuryakov 2008-01-09 06:22:55 PST
See also: <rdar://problem/3554361>.
Comment 5 Ahmad Saleem 2022-06-24 09:26:12 PDT
Created attachment 460478 [details]
All browsers differ

I am not clear on expected result or web-spec but based on attached test case, as can be seen in attached screen, all browsers slight differ with each other.

I have highlighted few cases, where Safari was different compared to others and also similarly for Firefox, where it was different from other two browsers.

I think it would be ideal to align all browsers to avoid any pitfalls. Thanks!
Comment 6 Myles C. Maxfield 2022-06-24 21:02:54 PDT
The spec says we shouldn’t honor postscript font names in the font-family property. However, as far as we know, WebKit must continue doing this because of content compatibility.

The spec also says that postscript names should be honored in the src:local() function inside the @font-face block, which WebKit does correctly.