[Webmistress]

Checked out one of our blogs today and in FF & Chrome it is perfectly as it should be but in IE7 suddenly the text is HUGE and seems to be ignoring the set text sizes. It worked fine before today, other than adding some new postings nothing has changed on the blog at all.

I changed other things on the stylesheet like text colours etc and IE7 recognised and displayed these changes fine but any change to the font size remained totally ignored!

Any ideas what's gone wrong or what to do to rectify it?



ps. this blog hasn't been upgraded to 2.9

[Gaystoryman]

That is an odd one, what's the blog url so we can see. My first thoughts are a virus, or somehow the code got corrupted.

[Webmistress]

Here's the site

It is so odd as it works absolutely fine in FF & Chrome.....

[Gaystoryman]

have you tried uploading another copy of the stylesheet? sometimes they seem to get corrupted and that usually clears it up.

[Gaystoryman]

Is it the sidebar text that's gone wonky? or the post content font size? Might want to check the sidebar font in the stylesheet. I am seeing it off in both IE8 and 7

I use browsershots.org that gives me screenshots of a site in all browsers. you can select which one's to have them show.

[Webmistress]

It is the text right across the site, not just the sidebar but the main body text as well
I have re-uploaded the stylesheet, no effect
I have made changes to the stylesheet and it changes everything apart from the text size
I have checked the stylesheet for any errors and can't see any
I haven't actually made an changes to the coding since the blog initially went live and it was working fine yesterday

Actually it is IE8 I'm viewing it in

[VoyGeorge]

You might want to download a copy of the source, and pass that through Dreamweaver's validation feature. That can sometimes turn up a missing end tag. WHY a tag would be missing is hard to tell, but it could be a plugin or something else.

I passed the URL through the W3 validator, and the first two errors/warnings would be considered "fatal"

The W3C Markup Validation Service

It only works in Firefox and other Webkit-based browsers because those browsers are correcting for the error.

Others like

id=hidden

rather than id="hidden" (which it should be)

could cause problems depending on the browser.

Anyway, some of this can be corrected by going through the theme and making the necessary corrections but other things may be due to WordPress messing up (SEO pack, for example).

[Webmistress]

Ok thanks, it just seems very odd that nothing has been changed since the theme, etc was originally uploaded and no plugins have been upgraded. Will have a look again at the code.

[gonzogone]

along with VG's suggestion of validating the template code, you can also validate the CSS with The W3C CSS Validation Service

I just checked your CSS and it validates fine. Between HTML and CSS validation, they account for the largest number of problems related to wonky behavior between browsers in my experience. Start throwing in dynamic code via PHP and it can get really fun to correct...

Why it worked before and changed suddenly is anybodies guess - corrupted file someplace is likely

[VoyGeorge]

Good idea on the CSS validation.

I know the problem appears to have come out of the blue, but something these things happen. And, looking at the errors the W3 validator points out, the template/theme leaves something to be desired. It has a lot of rudimentary XHTML errors in it.

I think you'll find if you locate the first main H1 within DIV class="logo", and close the tag, it'll work again.

Though I think it's a good idea to correct the markup errors, you might be able to also ease some of the issues by using a HTML 4.01 DOCTYPE rather than XHTML. The difference is how strict the browser interprets the code.

[gonzogone]

Originally Posted by VoyGeorge

Though I think it's a good idea to correct the markup errors, you might be able to also ease some of the issues by using a HTML 4.01 DOCTYPE rather than XHTML. The difference is how strict the browser interprets the code.

good point, and you can also get there going with a transitional versus strict doctype. You almost have to balance how much HTML versus XHTML you have in the code. If you've got any XHTML, you can use transitional with it.

Unfortunately, I think there are a lot of people who don't understand what the doctype does for them and that's where some of these problems start...

[Webmistress]

Thanks for all your help guys! The H1 closing tag did it!!!!! I will look at any other bits as well but at least it looks normal again.

Why is it the harder and longer you stare at a problem you just can't get your head around a solution and see the problem!!

Thanks again

[Tigger]

AND

before you lot start having a go it was nothing to do with me

[jello]

Originally Posted by Tigger

AND

before you lot start having a go it was nothing to do with me

[gonzogone]

you know what the real solution is? We all need to organize and stop designing for IE, that way, people will stop using it and we can work with some standards!

glad it got sorted