W3C home > Mailing lists > Public > www-style@w3.org > August 2014

Re: [css-color] Exposing browser color parsing to JS

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 7 Aug 2014 16:33:30 -0700
Message-ID: <CAAWBYDBu82-aY1zrtc+zxqGh5Lio83HXdcVTAiNM9_pXWAdvMw@mail.gmail.com>
To: Florian Rivoal <florian@rivoal.net>
Cc: www-style list <www-style@w3.org>
On Wed, Aug 6, 2014 at 10:08 AM, Florian Rivoal <florian@rivoal.net> wrote:
> On Mon, Jul 14, 2014, at 01:00, Tab Atkins Jr. wrote:
>> Okay, the proposal is now specced:
>> <http://dev.w3.org/csswg/css-color/#apis>
>
> RGB, HSL and hex are different representation of the same color in the
> same color space, so having the conversion between each is cool, and
> does not require any assumption about color spaces. Everything is pretty
> much syntax level conversions.
>
> On the other hand, CMYK is a not a syntax conversion, but a different
> color space. Or to be more accurate, a different family of color spaces.
>
> I don't think it is appropriate to have implicit conversion between
> colors in an RGB color space and a CMYK color space without specifying
> which.
[snip]

I promoted this email to a top-level thread and replied there; see
"[css-color] Doubts on how we handle device-cmyk() and similar things"

~TJ
Received on Thursday, 7 August 2014 23:34:16 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 7 August 2014 23:34:17 UTC