Support » Fixing WordPress » huge fonts in IE (individual posts and sidebar)

  • Resolved writerspice


    I know this problem has been discussed a lot but I still haven’t found a solution.

    It’s the usual: my blog looks fine in every other browser but IE.

    In IE, the fonts get bigger and bigger as you scroll down the page and are also oversized in the sidebar. I’ve looked at the code on individual posts and there are no open headers or anything like that.

    The sidebar code looks fine to me, as well… (but I could be wrong – there’s a lot I don’t understand).

    If someone can help me, I would be extremely grateful…

    Style is 3k2, site is



Viewing 15 replies - 1 through 15 (of 16 total)
  • Hi Lauren,

    there are lots of validation issues on your site, not the least of which are things like rogue attributes.

    alt=’Man says “there’s no tomorrow”‘ has three apostrophes in it, so the alt attribute actually ends after ‘there’ and before the ‘s’… these are things you have to worry about.

    There are also loads of parsing errors, and before that there are opened div tags which never get closed, etc etc.

    You might want to fix those with the help of a validator, one by one, unitl your site validates – then it’ll be much more obvious as to what the cause of your problem is.

    Thanks so much for replying…

    A couple more questions.

    First is, would it fix itself if I changed themes?

    And I’ve gone to the validator site, but I’ve no idea what files it’s reading so I don’t know which file to go into to fix the errors… ! If you can tell me that, that would help loads!



    The errors look to be related to your posts, not the theme, so I think changing themes wouldn’t necessarily fix anything.

    Of course, you could be lucky and change to a theme which isn’t as badly affected… but that doesn’t really solve anything.

    if you plug your site into the validator, it’s looking at the same page your browser sees when you go there yourself.

    You should look at the surrounding text in the errors it hands out, and fix them one by one, from the top down.

    For instance, if it’s finding issues with your alt attributes, then edit whichever post of yours contains the image that’s referring to, and fix your alt attribute.

    …. then run the validator again, and so on…

    with that many validation problems this may take you a little while, but once it’s fixed it’ll be easier to maintain, and also MUCH easier to diagnose any weirdness.

    If it’s the posts, I don’t get why the sidebar is affected…

    And I know the validator sees the same page I’m seeing, but I’m not sure exactly where that is. Do you know what I mean?

    Like, I can look at the source code, but I’m not sure what exact file that is so that I can go in and change it… I think that’s such a basic question that it doesn’t make sense to people. If you think about how you’d explain it to a 5 year old, that might help :\

    Thanks, again.

    If it’s the posts, I don’t get why the sidebar is affected…

    The sidebar code typically comes AFTER all your post content, just that the layout instructions tell it to live side-by-side with the content.

    That’s why if you have broken content, the sidebar will be affected (even seemingly above the point where your content is broken)

    And I know the validator sees the same page I’m seeing, but I’m not sure exactly where that is. Do you know what I mean?

    Yes, I know what you mean. The page you see when you visit your site in a browser is assembled with a rather complex series of actions performed by wordpress.

    When you add content to your site, you’re adding it to a database, and to display that content the wordpress software then extracts it from the database, performs it’s magic, and stuffs it into whatever theme you happen to be using. All this happens behind the scenes to generate the ‘page’ you view when you hit your website.

    The validator sees only the result of this process, not any “files” you may or may not have uploaded.

    WordPress itself works, so you don’t need to worry about that. The only files you should be concerned with are those comprising the theme you’re using – and if the same issue happens when you change themes then you can likely ignore those too.

    The rest is all in your posts, and those don’t exist anywhere outside the database.

    By the way, while a five year old may look like they know more about your VCR than you do, they really have no idea how it works… and trying to explain it to a five year old would involve words like ‘magic’ 🙂

    Magic I get! That’s part of the problem…

    Could another part of the problem be that I’ve been willy-nilly using HTML? I use <br> quite often, like in the sidebar code, to space things. It’s what I know… But I’m seeing that this might be generating a lot of errors. Am I right about that? And if so, what’s the equivalent in CSS?

    I’ve tried to upload a new theme, as well. It’s ProSense and it’s in my themes folder but isn’t showing up in Presentation…. Clearly, I’m not having a good day 🙁

    Who knew you had to have a Computer Science degree to blog!!

    Thanks again for the help…

    your <br> tags will generate validation errors, but they won’t cause all your problems (there are worse things in there somewhere).

    You can continue to use manual breaks in your sidebar, but they should look like this:

    <br />

    XHTML requires that all tags be opened and closed, and this is their way of dealing with tags which don’t have partners. Images should also be terminated that way (in fact any tag which is not a pair, like <hr /> etc…)

    Really, what you’re doing here is web design using a very complex PHP platform. If you were just blogging, all you’d be doing is putting text into posts, but here you are playing with your sidebar…

    Blogging is easy, customisation is the hard part. 🙂

    You’ll get there though… you just need to retain your patience and eat the elephant one bite at a time.

    I should also add that valid code has long-term benefits for your site, in terms of the way search-engines index your work.

    spending the time really is an investment in the future of your site.

    Thanks so much, Ivovic, for all your help. I really appreciate it!

    If I can just ask one more question… Should my pages have some header that makes them XHTML Transitional? B’c that’s one thing the Validator is saying…

    Thanks – have a great weekend.


    They have the doctype xhtml transitional.

    The message for you ther is the not valid part 🙂

    yes, your pages have the appropriate doctype declaration.

    The validator (and other software which sees your page) uses this declaration to determine how to treat your website. It’s really a lot like putting “do not bend” on envelopes with photos in them.

    Transitional is somewhat less restrictive than Strict, as the name suggests, which sounds like it might be best for your needs.

    Thanks… … 😉

    As you can tell, I’m losing my mind – winking for no good reason!!!!

    At this point in the day, the above reads like a Medieval riddle, but I will keep on and hopefully it will all eventually come clear.

    But regardless, thanks for the help!!

    moshu is a great reason to wink! 😉

    … and knowing when to take a break is a valuable skill 🙂

    Every well-coded web document needs to have a DTD (=document type declaration) or doctype declaration at the very top.
    Here is a list (just FYI) of different DTDs.

    Now, the validator “looks” at your code and because the validation rules for different DTDs are different… it will check your site according the the existing DTD’s rules.

    You don’t really need to know all this stuff… but since asked 🙂

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘huge fonts in IE (individual posts and sidebar)’ is closed to new replies.