Ye it must be, i thought that so what I did was grab the new font family code, the whole lot and stick it in the (*) everything style, and the whole website changed font, so its def not the path, would you agree with that?
I’m not sure of the specificity of the * selector in css, I wouldn’t think it overrides a class and element combination.
Normally I would set the default font on the body or html, this will have lesser specificity than .blog-menu a
To check if this is a specificity issue and not a @font-face issue, change it to some common system font to test it.
You need the @font-face declaration for the custom font to work, which is why your 2nd effort failed. But if your first worked, then your selector is probably wrong.
Just to be sure, you’ve got structure like this, correct? That’s what your selector is expecting…
<div class="blog-menu">
<a href="http://www.somewhere.com">Link should be styled</a>
</div>
Maybe better if I show you the site, its wordpress so it might be something there, but its the main nav in the red bar at the top that i want in the specialist font
@SamA74 may be right and the * may be causing the issue…why I don’t know since the specificity on the .blog-menu a should be higher, but when I inspected the element, I had to disable that line (all three times - you need to figure out why your stylesheet loads three times).
Try changing that first line to use body, html instead.
@PaulOB - why would his generic selector be overriding the more specific selector - either way (identifier and math), it should be picking up the other line…
I’m a bit puzzled why lucida sans is winning over your custom font, you even have !important on it which should trump everything, and its on a later line.
I’m still a bit suspicious of the * selector, as it means everything.
It’s definitely the culprit as if I disable them in the css, it sets the style right. What I don’t understand is why the .blog-menu a (which is the same as *.blog-menu a) doesn’t override it
I changed * to body, html and it still didn’t over-ride it, and yes I added !important and that didn’t do anything either, strange isn’t it, seems to straight forward.
could it be that the navbar is fed its font style from another class perhaps, and that is over riding my special font, but I thought that at the start and thats why i have added the font style down to the lowest class or indentifier I could, its right on the ‘a’ class style
Hi gandalf, I cant work that out, I just picked up on that from a previous post and was looking, in the mean time, its probably miles off but tried this but didnt work
* not(.blog-menu a){
font-family:"Lucida Sans Unicode", "Lucida Grande", sans-serif;
}
Nope cant work out why its calling it 4 times, all the files in the child folder have no link to style.css in them, so thats checked, cant think anywhere else