Search Display Problems In IE

I’m having troubles with search results displaying improperly in IE (6 - at least). The results show in a bold and odd-looking font. I’ve tried styling the div but it doesn’t seem to work.

You can check it out here: http://www.pdrlaw.net (do a search for ’chagnon’)

Thanks in advance.

Looks fine and all the same here in FF 2.0.0.8, IE 7, IE 6, Opera 9.24 on WinXP SP2

That’s strange. I’m using IE 6 to view the site and the font for the search results is bold and jjagged. Thanks for the feedback

The CSS Validator is throwing some font-family errors for your CSS: http://jigsaw.w3.org/css-validator/validator?profile=css2&warning=2&uri=http%3A%2F%2Fwww.pdrlaw.net%2Fcss%2Fmain.css

And also the HTML Validator shows some errors: http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.pdrlaw.net%2FSearch

Not sure if they are related, but i recommend to fix things like that first.

I’ve check the HTML errors. They don’t exist.Checking the CSS errors. Thanks.

Hmm. So the HTML errors don’t exist? Sorry, that’s a bit strange answer. I recommend having a better look, because I see the errors. But if not even the validator can convince you there’s a problem, I probably can’t either.

For IE6 there are two quick things you could do to check these are not the issues

1. On html,body, move the font styling to just body tag (Not really sure why I am suggesting this except for some reason I remember having a similar issue with IE6 which was fixed when I applied the fonts just to body tag)
2. Check is not a specificality issue, again I seem to recall IE can arrive at different results to FF. You could try using this also http://www.rebelinblue.com/specificity.php

if nothing else it would eliminate those two possibilities.

BTW:@ I was not convinced the HTML validator was correct. Some of the errors is states look fine in view source

Quote from: edge at Oct 25, 2007, 02:59 PM

BTW:@ I was not convinced the HTML validator was correct. Some of the errors is states look fine in view source

Sorry, but I don’t get you guys. There are 10 opening div’s and 11 closing div’s on the search page. Then we see constructs like this:



To me, these things are first to eliminate when dealing with display problems.

In the CSS we see font definitions for H1 like this:



In my experience, it’s impossible to track down display problems in different browsers without addressing issues like that first. When presented with invalid code, the behavior in a browser becomes unpredictable. Just my two cents ...

I always forget that I don’t need the UL - LI mark-up with Wayfinder. Fixed the H1 font styling too but no change. I’ll work on it more later. Thanks for the help.

fair point nightsignals,

I had a look at a couple the validation errors generated and they were ok in source but it was not a detailed look so I hold my hand up on this occasion.

of course one error can also sometimes generate others in the validator, which can be a red herring also.

Apologies on my part jwmsales for not spending enough time on investigation before I posted my comments