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

RE: [css-color-4] Renaming gray()

From: George Weilenmann <george.weilenmann@insightsoftware.com>
Date: Wed, 23 Jul 2014 22:52:14 +0000
To: Tab Atkins Jr. <jackalmage@gmail.com>
CC: Kornel Lesiński <kornel@geekhood.net>, www-style list <www-style@w3.org>, Lea Verou <lea@verou.me>
Message-ID: <6831C5AB7FFA4047B0D01BD5BC2530B77416B4FD@mbx500-u1-lo-1.exch500.msoutlookonline.net>
@TJ *agreed*, it could be an alias, although if I am remembering from other threads aliases are being actively avoided.
I was trying to provide possible compromise from the points that I had seen raised so far, and now I'll gracefully bow back out.

George Weilenmann
IT Help Desk | CRM Customization | Portal Developer
 Office +1 303.800.5027| Mobile +1 720.940.0974
5613 DTC Parkway, Suite 570, Greenwood Village, CO 80111

-----Original Message-----
From: Tab Atkins Jr. [mailto:jackalmage@gmail.com]
Sent: Wednesday, July 23, 2014 4:47 PM
To: George Weilenmann
Cc: Kornel Lesiński; www-style list; Lea Verou
Subject: Re: [css-color-4] Renaming gray()

On Wed, Jul 23, 2014 at 3:27 PM, George Weilenmann <george.weilenmann@insightsoftware.com> wrote:
> I know I am an outside here, but as a suggestion...
> How about leaving gray() as is and adding graying(), graying implies an actionable making a distinction between the two.
> Where gray(%) resolves to the shade of gray rgb(%,%,%) And Where
> graying(%) acts as a blender towards gray(50%)

While it's a little less obviously named, turning a color gray is just reducing its saturation, and so can be done via the color() function and the saturation() adjuster, like "color(red saturation(- 20%))".

Disclaimer: This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system.

Our company accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

InsightSoftware.com is a Trading Name of 'InsightSoftware.com Limited',Registered in England No. 2860790 at 53-55 Uxbridge Road, Ealing, London, W5 5SA, United Kingdom, VAT Number: GB 766 8160 95
Received on Wednesday, 23 July 2014 22:52:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:44 UTC