Posted By Joseph Craig on 24 Feb 2010 7:40 AM
Styles defined in your skin.css file should override those defined in _default.css.
If you have a single portal installation, though, you can delete definitions from _default.css without too many worries.
Is there something we have to do to get this behavior?
The default.css seems to take priority on my site. My specific example occurs in the A:links style. I see it being disabled in the developer view in IE. It laves the default.css as active and marks out the conflicting skin.css as well as the div css I placed.
Edit: I found my issues to be that the font color css was not taking over for the A:link color.