I have to agree with Hector here. I think blueprint should not be defining colors, as most design has a specific set of colors to use and we either have to redefine the blueprint colors OR change the original CSS (not my idea of a good use of a framework)
Just my 0.05c Regards Scott Warren Ocom Software - Quality Speciality Software web | http://www.ocom.com.au On Tue, Aug 31, 2010 at 10:42, Hector Virgen <djvir...@gmail.com> wrote: > I suggest removing "a:hover" and any other a:pseudo-selector styles and > providing just plain old "a" styles. While I appreciate that BP provides > sensible defaults, it creates extra work (however minimal) for a web > designer when they need to adjust link colors for their site. For example, > if the site's links should be green, a designer would need to overwrite at > least 3 CSS selectors: > > a, a:focus, a:hover{ > color: green; > } > > Just my 2c :) > > -- > *Hector Virgen* > Sr. Web Developer > Walt Disney Parks and Resorts Online > http://www.virgentech.com > > > > On Mon, Aug 30, 2010 at 7:26 AM, rebus_ <r.dav...@gmail.com> wrote: > >> On 28 August 2010 16:45, Christian Montoya <siro...@gmail.com> wrote: >> > On Fri, Aug 27, 2010 at 8:06 PM, 24/7 <2...@gmx.net> wrote: >> >> Good point. Maybe the whole text could be #313131, links underlined + >> #000 >> >> or #009ee0. Dark grey makes reading easier than black and black would >> stand >> >> out for the links (with the underline). That would be decent. In the >> other >> >> version I’d prever #009ee0 = cyan, because it’s not that hard, more >> friendly >> >> and pretty close to the default link color. >> > >> > When Blueprint was first launched, links were gray by default and >> > black when hovered. If my memory serves me correctly, I convinced the >> > original developers to change the default link color to some kind of >> > blue... and that's how we ended up in this current situation, where >> > links are dark blue by default and black when hovered. No one has ever >> > complained about this, until now, so let's make this thread the >> > official place for people to sound off: >> > >> > a:hover should be... >> > >> > - black (#000) >> > - the same as a:link >> > - a lighter blue (like cyan) >> > - something else... >> > >> >> The longer the list get’s, the closer I am to release 0.9.2 on my own. >> > >> > I've posted requests to the list in the past asking for more >> > contributors. The truth is that there is only a small handful of >> > people who have been contributing over the past year, and there is a >> > long list of updates that need to be made to the Blueprint core. >> > Furthermore, github.org has a great fork & pull-request system that >> > allows anyone to make updates to Blueprint, by working on their own >> > fork, and then submit those changes to the core, by sending a >> > pull-request to Joshua Clayton (not me). So if you want to help make >> > 0.9.2 a reality, and have my eternal gratitude, well, now you know >> > how. >> > >> > -- >> > -- >> > 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<blueprintcss%2bunsubscr...@googlegroups.com> >> . >> > For more options, visit this group at >> http://groups.google.com/group/blueprintcss?hl=en. >> > >> > >> >> Hi everyone, >> >> I have thought about this in several occasions but never gotten around >> to do anything about it. >> >> Currently we have (i think :): >> >> a:focus, >> a:hover { color: #000; } >> a { color: #009; text-decoration: underline; } >> >> First, I would like to see :hover, :focus and :active (currently >> undefined) a bit brighter so it is easier to spot the change of colour >> thus recognizing the text as hyper link (I like red so I'll suggest it >> as my choice but I am no designer and not very good with colour >> picking). >> >> Second, I am of opinion that blue is ok colour for link itself since >> it has been the default colour for links in most browsers for ages. >> >> Third, perhaps it would be nice to introduce :visited in >> typography.css too? I would keep it same colour as link by default (i >> think you mostly don't want links changing colour in menus etc, while >> you would like to do that for some article list or something so you >> would define :visited only on that set of links, but I could be >> totally off here.) >> >> Maybe something like: >> >> a:hover, a:active {color:#F00} >> a, a:link, a:visited { color: #009; text-decoration: underline; } >> >> My -0,2€ >> >> -- >> Davor Lučić >> >> -- >> 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<blueprintcss%2bunsubscr...@googlegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/blueprintcss?hl=en. >> >> > -- > 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<blueprintcss%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/blueprintcss?hl=en. > -- 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.
