W3C home > Mailing lists > Public > www-style@w3.org > November 2001

WD-css3-color-20010305 comments

From: Etan Wexler <ewexler@stickdog.com>
Date: Fri, 30 Nov 2001 22:17:42 -0500
To: Web style list <www-style@w3.org>
Message-Id: <20011201031841.55BF413607E@server12.safepages.com>
Colors <http://www.w3.org/TR/2001/WD-css3-color-20010305>



3.1. Foreground color: the 'color' property 
<http://www.w3.org/TR/2001/WD-css3-colo
r-20010305#foreground>

"EM { color: rgb(255,0,0) }     /* RGB range 0-255   */"

Eliminate the range restriction.

"attr(X,color)"

The "color" argument of the function is unexplained.



3.2. Transparency: the 'opacity' property 
<http://www.w3.org/TR/2001/WD-css3-colo
r-20010305#transparency>

As discussed on the www-style (<http://lists.w3.org/Archive
s/Public/www-style/2001Nov/0043.html>, 
<http://lists.w3.org/Archives/Public/www-style/2001No
v/0044.html>, <http://lists.w3.org/Archives/Public/www-styl
e/2001Nov/0056.html>, <http://lists.w3.org/Archives/Publi
c/www-style/2001Nov/0061.html>), we should have 
opacity properties for the parts of the box:
'content-opacity',
'background-opacity',
'border-top-opacity',
'border-right-opacity',
'border-bottom-opacity',
'border-left-opacity',
'border-opacity' (shorthand),
'outline-opacity'.

"Value: 	<alphavalue> | inherit"

Introducing a new value type is unnecessary.  The value should be 
a <number> because any decimal number is a valid value.  
If desired, the computed value may be noted as <alphavalue>.

"Any values outside the range 0.0 (fully transparent) to 1.0 
(fully opaque) will be clipped to this range."

Add: "when computed".

"If the element is a container element, then the effect is as if 
the contents of the element were blended against the 
current rendering composite using a mask where the value of 
each pixel of the mask is <alphavalue>."

What is a "container element"?  Is this a leftover from the 
SVG specification?



4.2. Numerical RGB color values <http://www.w3.org/TR/200
1/WD-css3-color-20010305#numerical>

"EM { color: rgb(255,0,0) }      /* integer range 0 - 255 */
EM { color: rgb(100%, 0%, 0%) } /* float range 0.0% - 100.0% */"

Eliminate the range restrictions. 

"EM { color: rgb(255,0,0) }       /* integer range 0 - 255 */
EM { color: rgb(300,0,0) }       /* clipped to rgb(255,0,0) */
EM { color: rgb(255,-10,0) }     /* clipped to rgb(255,0,0) */
EM { color: rgb(110%, 0%, 0%) }  /* clipped to rgb(100%,0%,0%) 
*/"

Eliminate the range restriction and indicate that clipping occurs 
in actual, not computed, values. 



4.4.1. CSS2 User preferences for colors 
<http://www.w3.org/TR/2001/WD-css3-color-20010305#css
2-user>

"Although these are case-insensitive, it is recommended that 
the mixed capitalization shown below be used, to make the 
names more legible."

Although stoodly-caps are already in use in some keywords, it 
is recommended that the Working Group use hyphenation in 
the future, to make names more legible.



4.4.2. 'flavor' system color <http://www.w3.org/TR/2001/W
D-css3-color-20010305#flavor>

"Note. The computed value of a System Color keyword value is 
the keyword itself."

Why is this clearly relative keyword kept as a computed value? 
 This tramples the CSS model of property values.



4.5. Notes on using colors <http://www.w3.org/TR/2001/W
D-css3-color-20010305#notes>

Link to appropriate Web Accessibility Initiative specifications 
on authoring and on user agent design.
Received on Friday, 30 November 2001 22:18:44 GMT

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