CSS and links help needed!

[kellilicious]

CSS and links???
i have set my styles for links to be green when in normal, active and visited states and only to change when hovered. it works fine, but when i click on a link and then go back to the page with that link, the rollover action does not work unless i click my mouse on the page or refresh. how do i get the rollover state to work at all times even after the link is clicked and revisited?

the example is here;
http://www.keenerassociates.com/DRAFT/home.html

[moonman]

I've had a quick look at the css, and I can't see any problem with the code. Sorry

[Mark T.]

Could you post the portion of your CSS code where you defined the styles for your links?

[kellilicious]

here's the code taken from my stylesheet:


.bodylink { font-family: Verdana, Arial, Helvetica, sans-serif; color: #006666; font-weight: bold; text-decoration: none; font-size: x-small}
a.bodylink:link { font-family: Verdana, Arial, Helvetica, sans-serif; font-weight: bold; color: #006666; text-decoration: none }
a.bodylink:visited { font-family: Verdana, Arial, Helvetica, sans-serif; font-weight: bold; color: #006666; text-decoration: none }
a.bodylink:hover { font-family: Verdana, Arial, Helvetica, sans-serif; font-weight: bold; color: #99CCCC; text-decoration: underline }
a.bodylink:active { font-family: Verdana, Arial, Helvetica, sans-serif; font-weight: bold; color: #99CCCC; text-decoration: none }

[chillin]

try moving all of the a.bodylink:hover {...} portion below the a.bodylink:active {...} portion.

for some reason, css wont read the link stuff after hover haas been defined. or at least not in my travels


thanks,
chillin

[kellilicious]

i'd actually made changes since i posted that. this is actually the correct one that corresponds to the problem and the url I posted.

.bodylink { font-family: Verdana, Arial, Helvetica, sans-serif; color: #006666; font-weight: bold; text-decoration: none; font-size: x-small}
a.bodylink:link { font-family: Verdana, Arial, Helvetica, sans-serif; font-weight: bold; color: #006666; text-decoration: none }
a.bodylink:visited { font-family: Verdana, Arial, Helvetica, sans-serif; font-weight: bold; color: #006666; text-decoration: none }
a.bodylink:hover { font-family: Verdana, Arial, Helvetica, sans-serif; font-weight: bold; color: #99CCCC; text-decoration: underline }
a.bodylink:active { font-family: Verdana, Arial, Helvetica, sans-serif; font-weight: bold; color: #006666; text-decoration: none }

[chillin]

same thing still applies.

[kellilicious]

aaah haaaa......bingo!

how did you ever figure that one out? trial and error, i assume. would have never thought that would be it!

thanks you are a life saver!!

(p.s. do you know anything about dreamweaver and the show/hide layers option??)

[Mark T.]

There is a little rule of fist you could use.

At first a link is a link, it is not active or whatever. When clicked, the link becomes active immediately, and after that it is visited.
The hover attribute is a little extra, which should overrule all classes, so therefore it is mentioned last.

I always used that when I started out with CSS, now it has become habit to place them in the right order.

[kellilicious]

funny, someone on another forum told me to keep them in this order

link
visited
hover
active

but that's how they were originally and it didnt work until i switched hover and active.

it's good to know that these things make such a difference!

[webteacher]

Please try the following syntax:

bodylink a:link
bodylink a:visited
bodylink a:hover
bodylink a:active

L V H A is the correct order.

I was lecturing on this very topic the other day.

Please let me know if it works!!!!

Nancy

[kellilicious]

LVHA is what i originally had but it didnt work.

someone suggested LVAH which was the only syntax that did actually work.

i never would have thought this would make a difference!

[chillin]

glad to hear it works!

i found out by spending a good hour or so on it...
what a pain it was.

good luck.

[lloydi]

Well, that's a funny little quirk indeed. I have learned something new today. Seems that I've not had this error occur in my pages, but it could easily have happened - if it does, I'll know why now!