bug#25890: Default value of digits-per-component?

[Clément Pit-Claudel]

On 2017-03-29 22:36, Eli Zaretskii wrote:
>> Cc: Eli Zaretskii <eliz@gnu.org>
>> From: Clément Pit-Claudel <cpitclaudel@gmail.com>
>> Date: Wed, 29 Mar 2017 16:01:09 -0400
>>
>>> If the change I made is nevertheless deemed too drastic, then what are
>>> our alternatives?  The only one I could think of is to define a new
>>> function and deprecate color-name-to-rgb in favor of that new
>>> function, which will then display warnings when code using it is
>>> compiled, and eventually cause them to make changes in their code
>>> anyway.  Is that better?  Or are there any better ideas?
>>
>> It sounds much better to me: the current solution breaks all code silently
> 
> I'm not sure I understand how come all users of that function are
> suddenly broken.  A different result doesn't yet mean breakage, unless
> the caller actually expected the precise format the old version was
> producing, and relied on that.  Is that indeed so in the callers you
> saw?

For me, yes, definitely: I was producing HTML webpages with inline CSS and 
LaTeX documents.  Both of these got very confused when they started receiving a 
longer hex codes :)
I don't know about the uses on GitHub. 

Clément.