- From: Alexis Shaw <alexis.shaw@gmail.com>
- Date: Fri, 17 Sep 2010 18:11:40 +1000
- To: Christoph Päper <christoph.paeper@crissov.de>, "www-style@w3.org list" <www-style@w3.org>
Received on Friday, 17 September 2010 08:12:13 UTC
256 values is not enough, as the color space would be compressed. (you would have more like 100 valid values for sRGB) On 17 September 2010 18:10, Alexis Shaw <alexis.shaw@gmail.com> wrote: > I mean that the definition needs to be able to have more than 256 possible > values, more like 10000 possible values > > > On 17 September 2010 18:03, Christoph Päper <christoph.paeper@crissov.de>wrote: > >> alexis.shaw@gmail.com: >> > >> > you need to be able to use more than 8 bits of precision in these >> colorspaces, a percentage xx.xxx% ? stored as a fixed point 16 bit number? >> >> CSS in general doesn’t concern itself all that much how something is >> represented in memory, but how authors can specify something. So, although >> 24bit is enough to accurately store any specifiable color in the “#ABCDEF” >> and “rgb(0,127,255)” formats, UAs may store them within 48bit or somethig >> else. If they clip to sRGB, which seems reasonable for desktop browsers, >> 24bit would still be enough (if I’m not mistaken), as long as they can parse >> values outside that space. > > >
Received on Friday, 17 September 2010 08:12:13 UTC