Viewing 7 replies - 1 through 7 (of 7 total)
  • Moderator t-p

    (@t-p)

    start with sorting out markup errors.

    Thread Starter Princess_Giggles

    (@princess_giggles)

    That is a very interesting analysis you did. But as I stated, my code (all of it, html and CSS) works just fine on IE if I am viewing an individual post, page, or archives. It is only on the index page that the CSS does not work correctly.

    The only changes I made to the Twenty Ten style sheet where colors and a few margin amounts.

    Moderator t-p

    (@t-p)

    you may also want to validate your CSS here.

    Princess – are you using code in the stylesheet? Or ie.css?

    That is a very interesting analysis you did. But as I stated, my code (all of it, html and CSS) works just fine on IE

    Doesn’t matter if it works fine sometimes….. you have some validation errors. For instance:
    http://validator.w3.org/check?uri=http%3A%2F%2Fwww.missgiggles.com%2Fblog%2F&charset=%28detect+automatically%29&doctype=Inline&ss=1&group=0&user-agent=W3C_Validator%2F1.1#line-38

    line 35 opens an h1 element…… which is never closed, unclosed elements can cause all sorts of layout issues

    IE is notoriously picky about code errors. As long as there are vaidation errors, output will be unreliable and unpredictable. Get the code valid, then if there are still issues we can sort them out….

    You won’t be able to fix everything, but unclosed elements are definitely important

    Thread Starter Princess_Giggles

    (@princess_giggles)

    Mr. Voodoo,

    I beg to differ. The fact that it does work some times and not others matters completely. In fact, that it works some times and not others is the entire problem. If IE is so picky, why doesn’t it have problems on all of the pages/posts/archives? It doesn’t. Only on the index.

    The point I was trying to make, is that your output will be unreliable because you have shoddy code.

    We can’t troubleshoot what causes the problems, because we don’t know what effects your crappy code edits are having.

    So first, you need to fix the code that we know causes problems. Once that is fixed we can move on…..

    Like I said, unclosed elements will definitely throw IE for a loop,.

    Upon investigating your site, it seems your single post view doesn’t use the h1 tag which is unclosed. Only your index does. So I will defer to my original post. Validate your code. Close your h1

    </h1> above </div><!-- #branding --> will probably do wonders

    Your index page has many more errors than your single page….. not a coincidence

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Index page displays wrong in IE’ is closed to new replies.