W3C home > Mailing lists > Public > www-style@w3.org > March 2010

Re: [css3-fonts] opentype font feature support

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 18 Mar 2010 07:49:44 -0700
Message-ID: <dd0fbad1003180749k770317cfj5af6a4e468ac42f0@mail.gmail.com>
To: rfink@readableweb.com
Cc: Thomas Phinney <tphinney@cal.berkeley.edu>, John Daggett <jdaggett@mozilla.com>, Christopher Slye <cslye@adobe.com>, www-style <www-style@w3.org>
On Thu, Mar 18, 2010 at 5:39 AM, Richard Fink <rfink@readableweb.com> wrote:
> Tuesday, March 16, 2010 8:23 PM <jackalmage@gmail.com>:
>>When we have UA-specific behavior like this, the convention seems to
>>be to use 'auto' rather than 'normal', right?  'normal' implies
>>determinism in the application of the property.
> Tab,
> Tell me what you mean by "determinism in the application of the property" as a deciding factor in choosing "auto" versus "normal" to mean what, in other contexts outside of CSS, is often "default".
> Do you mean that if the behavior is loosely defined and there's a lot of wiggle room for the UA, "auto" is preferred?

Yes, that seems to be a pattern I've noticed.  Whenever we have a
default value that allows some UA choice in what precisely happens, we
tend to gravitate toward 'auto'.

Received on Thursday, 18 March 2010 14:50:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:43 UTC