2012/1/10 Marat Tanalin | tanalin.com <mtanalin@yandex.ru>:
> 10.01.2012, 20:14, "Tab Atkins Jr." <jackalmage@gmail.com>:
>> On Tue, Jan 10, 2012 at 7:16 AM, Matthew Wilcox <elvendil@gmail.com> wrote:
>>
>>> That sounds great.
>>>
>>> I'm having a problem right now with a poor font stack in CSS. There's a menu
>>> that with standard fonts is FAR too large and so the display breaks
>>> terribly. Once the right font is loaded it's ok. But I can't detect which is
>>> actually being used so I can't correct layout. x-height adjustments may not
>>> work on their own because the character widths are different for a given
>>> x-height, which would still result in unwanted wrapping.
>>>
>>> For reference: http://testing.pulse3k.com (please note this is a work in
>>> progress and will change quickly. Please note that this is also a private
>>> URL, please don't use this for anything other than checking font behaviour.)
>>>
>>> If you've got NoScript installed it'll block the @font-face font and you
>>> will see the main banner nav is terrible. Once allowed, it looks correct.
>
>> and again remove the padding from the <a>s.
>
> Just in case: padding for block links is usually used intentionally to improve usability by significant increasing clickable area of link. So padding just cannot be removed without affecting usability.
Believe me, I know; I've done my time as a webdev. Setting the <a>s
to display:block solves the issue flexibly.
~TJ