>> >> I think you need to declare both the custom font /and/ its fallbacks on >> H1. For example, if the custom font for h1 is a slab-serif, and the font and >> fallbacks declared on the body declaration are sans, in all likelihood h1 >> will render a /serif/ in browsers and device browsers not supporting >> @font-face [unless perhaps if the user has declared sans as the default font >> in her browser preferences, or has a user style sheet with sans as default. >> ~d >>
Actually that's NOT what you are saying, is it! :-0 OK, I re-read that. Full stack it is. Thanks! -- Tom Livingston | Senior Interactive Developer | Media Logic | ph: 518.456.3015x231 | fx: 518.456.4279 | mlinc.com ______________________________________________________________________ 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/
