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

Re: A CSS equivalent of HTML's DOCTYPE trigger

From: Marat Tanalin | tanalin.com <mtanalin@yandex.ru>
Date: Tue, 10 Jan 2012 20:39:10 +0400
To: Tab Atkins Jr. <jackalmage@gmail.com>
Cc: Matthew Wilcox <elvendil@gmail.com>,Jon Rimmer <jon.rimmer@gmail.com>,"www-style@w3.org Style" <www-style@w3.org>
Message-Id: <12691326213551@web146.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.
Received on Tuesday, 10 January 2012 16:42:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:09 UTC