[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#25890: `color-values` gives wrong value
From: |
Eli Zaretskii |
Subject: |
bug#25890: `color-values` gives wrong value |
Date: |
Wed, 01 Mar 2017 05:43:36 +0200 |
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: Rasmus <rasmus@gmx.us>, 25890@debbugs.gnu.org
> Date: Wed, 01 Mar 2017 00:42:02 +0100
>
> With that patch, for me in the recipe of bug #24273, it makes a
> difference; now
>
> (color-name-to-rgb "#ffffff")
> ==>
> (0.9961089494163424 0.9961089494163424 0.9961089494163424)
>
> and
>
> (color-name-to-rgb "white")
> ==>
> (1.0 1.0 1.0)
That's what should happen, yes.
> For the recipe of this bug report, the values are the same as without
> the patch.
>
> I guess this is what you expected.
Yes, expected. color-values were not affected by the change, it's
just that color.el is now consistent with what color-values returns.
> But is it ok that "#ffffff" is not equivalent to "white"?
Yes. There's no other way, really, on systems where "white" has 3
16-bit components with all bits set, when color-values is called.