W3C home > Mailing lists > Public > www-style@w3.org > February 2012

Re: Colour tweaking (was: Re: Agenda conf call 25-jan-2012)

From: Simon Fraser <smfr@me.com>
Date: Tue, 07 Feb 2012 16:39:23 +0100
Cc: Chris Lilley <chris@w3.org>, CSS public list <www-style@w3.org>
Message-id: <BA87BC69-1231-4800-B6BB-7940EE444C3D@me.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
On Jan 25, 2012, at 5:21 PM, Tab Atkins Jr. wrote:

> On Wed, Jan 25, 2012 at 8:11 AM, Chris Lilley <chris@w3.org> wrote:
>> On Tuesday, January 24, 2012, 9:03:21 PM, Daniel wrote:
>> 
>> DG> 5. Color tweaking in CSS
>> DG> ------------------------
>> 
>> DG> Color tweaking (darkening for instance) is a request we get all
>> DG> the time from the author's community. I think we should (a) have
>> DG> a complete and detailed message explaining why we can't have it
>> DG> in CSS (b) or really start thinking about it. I also think our
>> DG> current position about it (does not exist in CSS) is indefendable
>> DG> in the long run.
>> 
>> DG> http://lists.w3.org/Archives/Public/www-style/2012Jan/0942.html
>> 
>> Isn't this something that CSS Filters already does?
>> 
>> You can lighten, darken, hue rotate, desaturate already using the filter syntax.
> 
> That lets you lighten/darken/etc an entire particular element.  It
> doesn't help the use-case of tweaking a color that is then used
> throughout the document (like a variable), or of tweaking the color
> used in a single property in an element.

I also think if we had lighten() and darken(), we could use them to define
exactly how groove, ridge, inset and outset borders should be rendered.
The spec currently talks vaguely about "slightly lighter and darker", and
we have not had cross-browser compatibility for these types of borders.

Simon
Received on Tuesday, 7 February 2012 15:44:42 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:50 GMT