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

Re: [cssom-view] colorDepth/pixelDepth, match implementations or theoretical purity?

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 19 Jun 2013 15:58:42 -0700
Message-ID: <CAAWBYDAB5DtJ_1J5XO9fpPTaX2CraWW1FRpbajdVjyiOzsmLKg@mail.gmail.com>
To: "L. David Baron" <dbaron@dbaron.org>
Cc: Simon Pieters <simonp@opera.com>, "www-style@w3.org" <www-style@w3.org>
On Wed, Jun 19, 2013 at 3:07 PM, L. David Baron <dbaron@dbaron.org> wrote:
> On Wednesday 2013-06-19 14:49 -0700, Tab Atkins Jr. wrote:
>> These features are basically useless.  Nearly every device that
>> matters has 24/8 color, and even for those that have 30/2 or something
>> more exotic, you need the entire browser and rendering pipeline to
>> support it before it makes sense to return the value to authors.
>>
>> I support speccing colorDepth/pixelDepth as a static 24 for now, and
>> separately, checking usage to see if we can just drop it.  I support
>> *not* implementing alphaDepth at all, for the reasons stated above.
>
> I'm skeptical about hard-coding it to 24.  I think a bunch of mobile
> devices these days are still using 16-bit color (though I'm not
> sure).  We also have media queries for roughly the same information.
>
> I tend to think if it's something that authors never care about we
> wouldn't have added it to two different properties on the screen
> object and to media queries.  Though maybe I'm wrong.

I assume the MQs should be frozen in the same way and/or dropped.

~TJ
Received on Wednesday, 19 June 2013 22:59:30 UTC

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