W3C home > Mailing lists > Public > www-style@w3.org > January 2012

Re: A CSS equivalent of HTML's DOCTYPE trigger

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 10 Jan 2012 09:14:43 -0800
Message-ID: <CAAWBYDBeMMziJzHa4xNGjv1OpQcTGmLheqvLi9dujV98cZRJxg@mail.gmail.com>
To: "Marat Tanalin | tanalin.com" <mtanalin@yandex.ru>
Cc: Matthew Wilcox <elvendil@gmail.com>, Jon Rimmer <jon.rimmer@gmail.com>, "www-style@w3.org Style" <www-style@w3.org>
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.

Received on Tuesday, 10 January 2012 17:15:45 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:08 UTC