W3C home > Mailing lists > Public > www-style@w3.org > August 2013

Re: [css3-fonts] font-size-adjust auto issue

From: Sylvain Galineau <galineau@adobe.com>
Date: Tue, 27 Aug 2013 16:04:57 -0700
To: "Levantovsky, Vladimir" <Vladimir.Levantovsky@monotype.com>, Jonathan Kew <jfkthame@googlemail.com>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <CE427DD5.BA33%galineau@adobe.com>

On 8/27/13 1:04 PM, "Levantovsky, Vladimir"
<Vladimir.Levantovsky@monotype.com> wrote:

>I like the idea of allowing 'font-size-adjust' use the specific font as a
>value target, e.g.
>font-family: Verdana, Futura, sans-serif;
>font-size-adjust: Verdana;
>Allowing a specific, predefined font be set as a target will in fact make
>this property easier to use and have much more deterministic behavior,
>but there is always a risk that the font in question may not be available
>on a platform or it may be a webfont that needs to be downloaded first.

True. However, I like the fact that it's way easier to explain and use
than the current property. In most cases it'll work. But when it doesn't
work right, will it really be worse than what you get when your carefully
chosen font-size-adjust ratio goes weird across platforms?

>However, there is one caveat with allowing generic-family names (i.e.
><serif>, <sans-serif>) as value - the results of the adjustment will
>still be unknown. It is an improvement compared to using the 'auto' value
>but a very marginal improvement nevertheless.

True. But if you set this property to a generic family name  you are
explicitly throwing up your hand in the air and asking for a random
result. I don't think we should worry about things getting weird when
people use values that maximize the odds of weird.

>> -----Original Message-----
>> From: Sylvain Galineau [mailto:galineau@adobe.com]
>> Sent: Tuesday, August 27, 2013 3:26 PM
>> To: Jonathan Kew; www-style@w3.org
>> Subject: Re: [css3-fonts] font-size-adjust auto issue
>> On 8/26/13 7:59 PM, "Jonathan Kew" <jfkthame@googlemail.com> wrote:
>> >
>> >Alternatively, I still think my earlier suggestion of allowing
>> >font-size-adjust:<generic-family> would be an improvement over <auto>,
>> >in that it would be clearer to authors that they're explicitly asking
>> >the browser to adjust the sizing of whatever font(s) are used to
>> better
>> >match one of its defaults.
>> I like this; font-size-adjust is imo usability-challenged, whatever one
>> thinks of the auto value. Calculating the right ratio generally
>> involves authors going through various hoops and experiments to guess
>> the right number. Which, as pointed out, may end up not working so well
>> on other platforms.
>> Specifying the font family whose x-height you want to use seems both
>> far more usable and closer to the design intent. Well, except for the
>> property name which no longer seems quite right. (Bikeshed!)

Received on Tuesday, 27 August 2013 23:05:26 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:14 UTC