Bug 7709

Summary: WebKit only uses PostScript font names for CSS fonts
Product: WebKit Reporter: Daniel J. Wilson <djw>
Component: TextAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Minor CC: ahmad.saleem792, ap, hyatt, ian, mitz, mmaxfield, nickshanks, rniwa
Priority: P3    
Version: 420+   
Hardware: Mac   
OS: OS X 10.4   
URL: http://blog.wilsonet.com/archives/2006/03/10/future-condensation/
Attachments:
Description Flags
test case
none
All browsers differ none

Daniel J. Wilson
Reported 2006-03-10 16:13:07 PST
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.
Attachments
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
View All Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2006-05-03 05:23:40 PDT
Created attachment 8092 [details] test case
Alexey Proskuryakov
Comment 2 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).
Nicholas Shanks
Comment 3 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 ;-)
Alexey Proskuryakov
Comment 4 2008-01-09 06:22:55 PST
See also: <rdar://problem/3554361>.
Ahmad Saleem
Comment 5 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!
Myles C. Maxfield
Comment 6 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.
Note You need to log in before you can comment on or make changes to this bug.