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

Re: WD-css3-color-20010305 comments

From: Chris Lilley <chris@w3.org>
Date: Mon, 03 Dec 2001 07:23:37 +0100
Message-ID: <3C0B1A69.D67CC50C@w3.org>
To: Etan Wexler <ewexler@stickdog.com>
CC: Web style list <www-style@w3.org>


Etan Wexler wrote:
> 
> Jens Müller pondered in response to me:
> 
> >> "EM { color: rgb(255,0,0) }     /* RGB range 0-255   */"
> >>
> >> Eliminate the range restriction.
> >
> > Why?
> 
> If the range restriction really existed, the declaration
> "color: rgb(300, 0, 0)" would be invalid and ignored.  Instead,
> CSS1 (<http://www.w3.org/TR/REC-CSS1#color-units>)
> dictates that user agents accept the declaration and clip the value
> to the sRGB gamut.  CSS2 (<file://localhost/h/www.w3.org/T
> R/REC-CSS2/syndata.html#color-units>) and CSS3
> (<http://www.w3.org/TR/2001/WD-css3-colo
> r-20010305#numerical>)  are even more lax, dictating that
> user agents accept the declaration and leaving clipping as an issue
> of the device gamut.

Yes, though its not a case of being lax. Its a caseof preserving color
inmformation - those could be real printable colors, though oyutside the
sRGB gamut.

> CSS1 clips computed color values while CSS2 and CSS3 clip
> actual color values. 

Yes.

>  In no case does CSS impose a range
> restriction on specified color values.  Therefore we should
> eliminate the stated range restriction.

Right. Those comments added to the CSS2 spec are contrary to the actual
word of the CSS2 spec and should be removed 9should not have bee there,
in fact).

-- 
Chris
Received on Monday, 3 December 2001 01:23:38 GMT

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