Re: Downloadable fonts and image replacement

Håkon Wium Lie wrote:
> Now, if webfonts are introduced along with text-replacement there
> might be a conflict. Consider this example:
>   h1 {
>     content: url(img/100x100.gif), contents;
>     font-family: url(/fonts/, serif;
>   }
> In the above example, the order of preference is clear; first the
> image, then the webfont, and finally the generic "serif" font.
> However, it is not possible to express this order of preference which
> often makes more sense: webfont, image, generic font. One way to
> address this issue is to put the order of preference on one property:

You're missing an important part of the usual set of preferences:
Usually you want to /preferably/ use the font installed on the system,
if it's there. Any proposal needs for resolving this conflict needs
to address that as well..


Received on Monday, 1 May 2006 00:22:38 UTC