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

Re: [css4-color] Make the r/g/b components be <number> rather than <integer>?

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 15 Jun 2012 11:59:20 -0700
Message-ID: <CAAWBYDBaq=sKQ+JSu5si1q0dOnRXxJSwN6E8rmQi6ECJHXmtqg@mail.gmail.com>
To: Rik Cabanier <cabanier@gmail.com>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, www-style@w3.org
On Fri, Jun 15, 2012 at 11:54 AM, Rik Cabanier <cabanier@gmail.com> wrote:
> It is relevant because it's specified in the spec. See the bottom section of
> http://www.w3.org/TR/CSS21/syndata.html#value-def-color:
> "All RGB colors are specified in the sRGB color space"
> sRGB is clipped to [0 1]
> The sentence that is causing the most confusion for me is:
> "Other devices, such as printers, have different gamuts than sRGB; some
> colors outside the 0..255 sRGB range will be representable (inside the
> device gamut), while other colors inside the 0..255 sRGB range will be
> outside the device gamut and will thus be mapped."
> Boris believes this means that <0 and >1 values are allowed

Boris is correct.

If you would like to continue this discussion, could you split the
thread?  This tangent is quite irrelevant to the original topic, which
was just about allowing <number>s instead of <integer>s in the
components of the rgb/a() function.

Received on Friday, 15 June 2012 19:00:09 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:00 UTC