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

Re: [css3-fonts] opentype font feature support

From: Brad Kemper <brad.kemper@gmail.com>
Date: Mon, 15 Mar 2010 09:39:22 -0700
Cc: John Daggett <jdaggett@mozilla.com>, www-style list <www-style@w3.org>
Message-Id: <F343B256-EDE5-48E1-BFA8-581694955444@gmail.com>
To: Thomas Phinney <tphinney@cal.berkeley.edu>

On Mar 15, 2010, at 8:59 AM, Thomas Phinney wrote:

> On Sun, Mar 14, 2010 at 11:52 PM, John Daggett <jdaggett@mozilla.com> wrote:
>> The keyword 'normal' is commonly used in CSS to indicate 'default', it's
>> the value a property will typically assume when it's not specified
>> explicitly.  I realize 'default' might seem more natural to some but
>> consistency with other CSS properties is important.
> Is it assumed that the effect of "default" can vary between UAs, or is
> the meaning of "default" usually specified by CSS?

There is no CSS-specific meaning to "default". Many properties have an "initial" value, which is the value to use if there is no other value given from the cascade or inherited. If a property uses a 'normal' keyword as one of its possible values,  it is often (but not always) the initial value (CSS defines this on a per-property basis). In addition, a UA may have a UA style sheet, which establishes some defaults for various document elements. For instance, even though 'font-weight' has an initial value of 'normal', an Web browser would have a style sheet in it that sets 'font-weight' to a non-normal value for STRONG elements and B elements:

strong, b { font-weight: bolder; }

Received on Monday, 15 March 2010 16:40:07 UTC

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