- From: David Hyatt <hyatt@apple.com>
- Date: Mon, 30 Apr 2007 16:29:58 -0700
- To: tina@greytower.net
- Cc: Maciej Stachowiak <mjs@apple.com>, "Philip Taylor (Webmaster)" <P.Taylor@Rhul.Ac.Uk>, HTML WG <public-html@w3.org>
On Apr 30, 2007, at 4:24 PM, Tina Holmboe wrote: > > Indeed. Such as the dynamic fonts that authors are screaming for, > which got added to CSS 2, removed from CSS 2.1 'cause the browsers > didn't implement it, and which have been re-introduced in CSS 3 > because *authors still want dynamic fonts*. > Authors wants it. Browser vendors didn't want to implement it. The > specification went with the authors, then the vendors, now with the > authors again. > Again this is patently false. This is one of the features I most want to implement. If anything blame for the failure of this feature to take off can be placed squarely at the feet of the CSS WG. If you'd talked to either me or Hakon (of Opera), you'd know that both of us feel very strongly that the Web needs downloadable fonts. I would *love* to implement this in WebKit/Safari. The problem is that the existing specification in CSS3 is horrible. Multiple browser vendors actually have agreed upon a way of doing this feature using URLs in the font-family property. However we have yet to implement it precisely because we had been trying to take a standards-based path (without much luck) at the W3C. dave (hyatt@apple.com)
Received on Monday, 30 April 2007 23:30:57 UTC