On Feb 10, 2011, at 5:26 PM, David Laakso wrote: > On 2/10/11 4:43 PM, Shawn Lawler wrote: >> On 2/10/2011 2:24 PM, David Laakso wrote: >>> >>> <http://chelseacreekstudio.com/makeover/journal/index.php> >>> >> >> >> Times New Roman (the first of your other typefaces which chrome is using on >> my machine when the web-font files aren't present) is either rendering >> beforehand, or is being used to calculate an initial line-height for that >> H1. Take a peak--gut your web-font rules and you might notice your >> "fallback" font is 'taller' than your web-font by approx. the same amount of >> the jump you're seeing. >> >> Shawn >> > > > Fallback fonts reset to only Georgia, serif; and, while this does not > entirely correct the issue-- it does make it far less noticeable.
I don't see the problem in Safari, but do see it in Firefox. You might find this info on fixing similar Typekit problem interesting -- http://blog.typekit.com/2010/10/29/font-events-controlling-the-fout/ -- Lowell Allen ______________________________________________________________________ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
