Fwd: New last call for CSS 2.1

This is a forwarded message
From: Bert Bos <bert@w3.org>
To: chairs@w3.org
Date: Thursday, December 2, 2010, 5:28:15 PM
Subject: New last call for CSS 2.1

===8<==============Original message text===============
Hello chairs,

During the current CR period for CSS 2.1, a number of new issues came 
up, causing enough changes that the CSS WG decided to publish another 
WD, before (hopefully) requesting PR status. The hope is that the 
revised CSS level 2 will then be Recommendation around March.

We will send the last call as soon as possible and comments will be open 
in principle for four weeks, i.e., until early January. Let us know if 
you need more time to review the document.

We have traditionally asked the following groups, or their predecessors, 
to review CSS 2.1: WAI PF, HTML, XSL, I18N Core, and SVG. Do they you 
want to do so again?

The internal draft is here:

    http://www.w3.org/Style/Group/css2-src/cover.html

The "Changes" chapter has all changes since 1998, but you might want to 
look specifically at section C.7[1], which has the changes relative to 
the current CR.

Some important changes are:

  - Stricter error recovery: A UA must no longer accept only valid
    extensions, but also handle syntactically invalid input exactly as
    the spec prescribes.

  - No absolute units anymore, except in print media. The units cm, in,
    pt, pc, and mm are no longer the ISO units, but are aliases for
    a certain number of px (96px in the case of in). The px itself is
    undefined (except in print media), but the previous definition is
    recommended.

  - The position of list bullets that would previously overlap floating
    elements, or that belong to list items with scrollbars, is made
    largely undefined, in preparation for new definitions in level 3.

  - Font family names containing numbers or punctuation must now be
    quoted. (Some browsers had trouble with declarations
    like 'font-family: Univers 56'.)

  - XML and HTML5 do not automatically remove insignificant white space,
    unlike SGML and HTML4, so CSS itself now defines what white space to
    ignore, specifically inside table elements, to avoid that HTML5
    documents create unexpected, empty table cells.

There is a mechanically generated diff version[2], but its readability 
varies a lot from chapter to chapter... 


[1] http://www.w3.org/Style/Group/css2-src/changes.html#errata3
[2] http://www.w3.org/Style/Group/css2-src/diffs-wd/cover.html



For the CSS WG,
Bert
-- 
  Bert Bos                                ( W 3 C ) http://www.w3.org/
  http://www.w3.org/people/bos                               W3C/ERCIM
  bert@w3.org                             2004 Rt des Lucioles / BP 93
  +33 (0)4 92 38 76 92            06902 Sophia Antipolis Cedex, France

===8<===========End of original message text===========


-- 
 Chris Lilley   Technical Director, Interaction Domain                 
 W3C Graphics Activity Lead, Fonts Activity Lead
 Co-Chair, W3C Hypertext CG
 Member, CSS, WebFonts, SVG Working Groups

Received on Thursday, 2 December 2010 17:58:16 UTC