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

[css3-color] editing of css3-color, its testsuite, and issues list

From: L. David Baron <dbaron@dbaron.org>
Date: Mon, 24 Mar 2008 16:42:52 -0700
To: www-style@w3.org
Message-ID: <20080324234252.GA5333@ridley.dbaron.org>

I've built up an issues list for css3-color at:
http://csswg.inkedblade.net/spec/css3-color that now contains my
proposed resolutions for all issues raised.  Most of these
resolutions should be non-controversial, but I think a few may
require discussion.  A brief summary of the issues list is as
follows:
 * A number of issues are about removing unimplemented features,
   which I propose doing (that is the main point of going back to
   last call).
 * A number of issues propose new features; I propose rejecting all
   of them for this version since this spec is already widely
   implemented and we'd like to advance to Recommendation sooner
   rather than later.
 * A number of issues are minor editorial corrections.
 * I propose in issue 5 clarifying the definitions of a number of
   system colors so that all readers of the spec don't need to
   reverse-engineer the color semantics from the Windows API.
 * I propose in issue 17 that color:currentColor's transformation to
   color:inherit should not be specified as being at parse time (I
   don't know of anything else in CSS that specifies this).
 * I propose rejecting issue 16, which argues that system colors
   should not be deprecated.
 * I propose no change for issue 22, mainly because I'm not sure
   what change would be needed (especially after unimplemented
   features have been removed), but I'm still open to editorial
   improvements.

If you know of any other issues, please raise them on www-style in a
message whose subject begins with "[css3-color]".  Feel free to add
them to the *end* of the issues list, with the URL of a message to
www-style.

I've started editing the draft to address these issues (although I
realize that the working group may disagree with my proposed
resolutions), and adding tests to the test suite to test the issues
they mention.  My editor's draft is at
http://dev.w3.org/csswg/css3-color/Overview.html
with the change log at
http://dev.w3.org/cvsweb/csswg/css3-color/Overview.src.html .
The test suite cvsweb interface is
http://dev.w3.org/cvsweb/CSS/css3-color-test-suite/
and the tests themselves (in unprocessed form) are at
http://dev.w3.org/CSS/css3-color-test-suite/src/ .
(I don't know how to make cvsweb show a changelist for an entire
directory tree to show the test suite change log.)

-David

-- 
L. David Baron                                 http://dbaron.org/
Mozilla Corporation                       http://www.mozilla.com/
Received on Monday, 24 March 2008 23:43:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:55:02 GMT