Pako--
I had a look at your style sheet (I couldn't open the download, so I simply viewed it through my browser... IE can't do that, but the Mac OSX-only Chimera can!
), and I see a few issues that can be sorted out.
First off, here's what you have regarding links:
_________________________
a:active {
font-family: "Times New Roman", Times, serif;
font-size: 12pt;
font-style: normal;
font-weight: bold;
color: #FF0000;
text-decoration: none
}
a:hover {
font-family: "Times New Roman", Times, serif;
font-size: 12pt;
font-style: normal;
font-weight: bold;
color: #336699;
text-decoration: underline;
line-height: normal;
font-variant: normal;
text-transform: none
}
a:link {
font-family: "Times New Roman", Times, serif;
font-size: 12pt;
font-style: normal;]
font-weight: bold;
color: #336699;
text-decoration: none
}
______________
Before I go on, one should note that your CSS should be written in the format that I've presented above... it makes it
much easier for yourself and others to read it.
Now, you say that you want the "a:visted" trait to be no different than the normal "a:link" trait, right? Well, there's a very,
very simple solution-- just make an a:visited rule, with all of the
exact same characteristics as your a:link rule! So, in your case, you'd have:
a:visited {
font-family: "Times New Roman", Times, serif;
font-size: 12pt;
font-style: normal;
font-weight: bold;
color: #FF0000;
text-decoration: none
}
Notice that it's exactly the same as the a:link rule, except for the first word, obviously.
Before I close this up though, I think that there are a lot of things that you can work on to clean up your style sheet, which is somewhat of a mess!
First off, you really should have a "body" rule in place, so that you can eliminate all of those redundancies. Remember, in CSS, when a child element is within a parent element, it not only follows its own rules set for it, but it
also inherits
all of its parent elements, unless they're overwritten by a certain specification. So, if you specify in the "body" rule
font-family: Times, you will never, ever have to do that again in any other of the various elements, unless you purposely want to overwrite it.
I'll use my CSS for an example:
__________________
body {
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 11px;
margin: 0;
padding: 0
}
a:link, a:visited {
color: #006300;
text-decoration: underline
}
a:hover, a:active {
color: #000000;
text-decoration: underline
}
h1 {
font-size: 13px;
font-weight: bold
}
div.normal {
padding: 3%
}
div.slink {
padding: 3%
}
div.slink a:link, div.slink a:visited {
color: #006300;
text-decoration: none
}
div.slink a:hover, div.slink a:active {
color: #000000;
text-decoration: underline
}
h2 {
font-size: 15px;
font-weight: bold;
color: #006300
}
___________
Notice that there are no unnecessary redundances (forget all of the div.slink stuff for one moment)-- for example, all of the "a:" rules don't specify font-size, family, etc., because they automatically inherit the properties of the body rule. In things like h1 and h2, I specify the sizes, weights, etc. because I am purposely changing them. Makes it much simpler, doesn't it?
As for the div.slink rules, if you read it, you'll figure out that it's basically everything that a div.normal rule is (
including the inheritance of the "body" properties), but I made it to overwrite the would-be-inherited a: properties, and changed them to not underline when in link and visited stages.
If you need any clarification, please ask!
-Sage
), but it truly is a top-notch book. 👍
:
).
