Bug 7709 – WebKit only uses PostScript font names for CSS fonts

• Status: NEW
• Component: Text

[Daniel J. Wilson]

When specified in a stylesheet, 'Futura Condensed' is rendered as Futura in WebKit (build 13244). Both Firefox (1.5.0.1) and Opera (9.0 preview) display the proper face.

[Alexey Proskuryakov]

Created attachment 8092 [details]
test case

[Alexey Proskuryakov]

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).

[Nicholas Shanks]

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 ;-)

[Alexey Proskuryakov]

See also: <rdar://problem/3554361>.

[Ahmad Saleem]

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!

[Myles C. Maxfield]

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.