W3C home > Mailing lists > Public > www-style@w3.org > March 2010

Re: [css3-color] #rrggbbaa annotation

From: Brad Kemper <brad.kemper@gmail.com>
Date: Fri, 26 Mar 2010 19:42:11 -0700
Cc: David Singer <singer@apple.com>, www-style list <www-style@w3.org>
Message-Id: <9C81AD7C-BAED-4F61-9971-1EE31C31F1EA@gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
But besides that, most tools with color pickers these days let you copy a hex value from them to paste in somewhere else. For instance, I sometimes use the color picker in PhotoShop to pick the color, then copy and paste the hex value into a text editor or Safari's developer tools. PhotoSHop also shows RGB, but that is in three different fields, so it would be three times the work to copy/paste (I do sometimes manually type the values and add an alpha component for rgba() though, but that takes an extra second or so!). 

I like the idea of #RRGGBBAA, and would have no problem picking the AA as hexadecimal.

On Mar 26, 2010, at 5:16 PM, Tab Atkins Jr. wrote:

> On Fri, Mar 26, 2010 at 5:11 PM, David Singer <singer@apple.com> wrote:
>> seems like if you expect to have colo(u)rs change, or more particularly you find the same constant several times in your code, you want to define your own named colo(u)rs, and then change one definition...(or use a variable, or something, waffle waffle...)
> True, CSS Variables would solve a lot of these problems.  If I only
> had to define colors once, and then could refer to them by name, it
> wouldn't be nearly as big of an issue.  Variables let you sweep a lot
> of pain under the carpet.
> ~TJ

Received on Saturday, 27 March 2010 02:42:48 UTC

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