On Tue, Aug 31, 2010 at 12:19 PM, Hector Virgen <djvir...@gmail.com> wrote:
> If we're going to keep a:hover can we at least make it blue? :)

I know it's pretty crazy to have a whole thread devoted to the color
of a:hover, but this has been very helpful. As Chris Eppstein said,
it's very hard to balance flexibility and attractive defaults.
Blueprint has always been meant to offer "great looking webpages" out
of the box, and as I've already said, and since the first version was
released by Olav Bjorkoy years ago, we've gradually gone about
removing things that are "frivolous" while trying to make things more
flexible and easier for designers to override as necessary. If you are
going to be defining your own link colors in CSS, then it is usually a
must for you to remember Lord Vader's Former Handle Anakin and
override all the link pseudo classes at once; basically, what I am
saying is that I don't think a:hover & a:focus fall under the realm of
frivolous defaults.* I think that for the next version of Blueprint
(which I am going to start working on tomorrow, provided I can get
past some awful terrible projects that have long overstayed their
welcome), I am going to go for something like:

a { color: SOME KIND OF BLUE; }
a:focus, a:hover { color: SOME KIND OF LIGHTER BLUE; }

with apologies to both Miles Davis and Deadmau5.


* though it's possible that what we really need is one or more forks
of Blueprint, that go about providing little more than a reset.css, a
stripped down version of typography.css/forms.css, and an optional,
generated grid.css, for those designers that are bound to override any
default colors defined by Blueprint. Think of this as Blueprint
Lite... actually, I think I might have suggested something like this
in the past. This could be more work than it's worth, however, and
will require some discussion with other core group members.

-- 
--
Christian Montoya
mappdev.com :: christianmontoya.net

-- 
You received this message because you are subscribed to the Google Groups 
"Blueprint CSS" group.
To post to this group, send email to blueprint...@googlegroups.com.
To unsubscribe from this group, send email to 
blueprintcss+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/blueprintcss?hl=en.

Reply via email to