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

Re: [css2.1][css3-fonts] keywords in unquoted font family names

From: John Daggett <jdaggett@mozilla.com>
Date: Wed, 23 May 2012 09:47:21 -0700 (PDT)
To: www-style list <www-style@w3.org>
Message-ID: <437493569.19639223.1337791641431.JavaMail.root@mozilla.com>

On the CSS WG call, the group resolved to accept the proposal to add
two changes to the CSS 2.1 errata related to the issue of reserved
keywords in unquoted font family names.  The original proposals were
outlined here: 

  http://lists.w3.org/Archives/Public/www-style/2012May/0630.html

We resolved on the changes but there were some requests to adjust the
wording of proposal 2, the tweak to the last paragraph of section 15.3
[1]. Based on the suggested adjustments, here's what I would propose
for the wording:

Existing:
  Font family names that happen to be the same as a keyword value
  ('inherit', 'serif', 'sans-serif', 'monospace', 'fantasy', and
  'cursive') must be quoted to prevent confusion with the keywords
  with the same names. The keywords 'initial' and 'default' are
  reserved for future use and must also be quoted when used as font
  names. UAs must not consider these keywords as matching the
  '<family-name>' type. 

Proposed:
  Unquoted font family names that happen to be the same as the keyword
  values 'inherit', 'default' and 'initial' or the generic font
  keywords ('serif', 'sans-serif', 'monospace', 'fantasy', and
  'cursive') do not match the '<family-name>' type. These names must
  be quoted to prevent confusion with the keywords with the same
  names. Note that 'font-family: Times, inherit' is therefore an
  invalid declaration, because 'inherit' in that position can neither
  be a valid keyword nor a valid font family name.

Regards,

John Daggett

[1] http://www.w3.org/TR/CSS21/fonts.html#font-family-prop
Received on Wednesday, 23 May 2012 16:47:55 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:54 GMT