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

Re: [css-color] . 12-Bit deep color support.

From: Marat Tanalin <mtanalin@yandex.ru>
Date: Mon, 09 Dec 2013 20:57:08 +0400
To: Simon Sapin <simon.sapin@exyr.org>, Daniel Beckstein <daniel@beckstein-rehau.de>, "www-style@w3.org" <www-style@w3.org>
Message-Id: <64081386608228@web22j.yandex.ru>
09.12.2013, 20:49, "Simon Sapin" <simon.sapin@exyr.org>:
> On 09/12/2013 16:43, Marat Tanalin wrote:
>
>> š09.12.2013, 17:45, "Simon Sapin"<simon.sapin@exyr.org>:
>>> šActually, CSS colors are not defined to be 8 bits. You can already use
>>> šnon-integer percentage (with any number of digits after the decimal
>>> špoint) in rgb() and rgba(). The exact rounding behavior and precision is
>>> šleft to the browser to decide.
>> šA sort of advantage of existing hex notation and its direct [in fact]
>> šmapping to 8-bit-per-channel color depth is that web-developer can be
>> šspecify an_exact_ šcolor, not some approximate one. It may be nice to
>> šstill have ability to specify an exact color for more deep color
>> šspaces.
>
> But not everyone one the Web will switch overnight to software and
> hardware that supports more color depth.

For those who haven't switched yet (and _only_ for them), browsers could degrade gracefully by rounding colors to more rough colorspace while still delivering exact colors to those who have capable hardware (number of such users will surely grow).

> Does it make sense to specify
> an exact value that is only exact for a fraction of your users?

I'm not sure it does _not_.
Received on Monday, 9 December 2013 16:57:38 UTC

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