IE8 - normal mode breaks the layout, Compatibility mode is ok

Discussion in 'CSS' started by Sunlust, Sep 9, 2008.

  1. #1
    Hi,

    Recently redesigned a template for Chatsworth Lodge No. 9053 Eastbourne
    It works nice, it looks nice, only problem is that when you run IE8 in it's normal mode it breaks the layout.

    In my company people already switched, IE8 is now another browser we have to test for.

    Let me know if you come up with any idea on why it breaks please.
     
    Sunlust, Sep 9, 2008 IP
  2. Stomme poes

    Stomme poes Peon

    Messages:
    3,195
    Likes Received:
    136
    Best Answers:
    0
    Trophy Points:
    0
    #2
    IE8 is NOT a stable-release browser. It was only released so that nerds like web developers could test proven sites against it, in order to send bug reports to the MS people so that when IE8 actually DOES get released, it will (hopefully) be able to be somewhere in the same ballpark as all the other browsers.

    Anyone who has officially switched to IE8, the Beta, needs to expect everything to look like crap. If you have customers complaining about how any particular page looks in IE8 (whether there really are problems in the site or not), tell them they're using an experimental browser which is still in testing phase, and to wait until Microsoft says they are done building it. They wouldn't drive an experimental car down the road, would they? Not with their kids in the back for sure.

    That said, IE8 isnt' the only one... the site generally looks ok in FF2 on Ubuntu Linux except the top... your menu is overlapping the title (although since your menu is see-through, maybe you meant to do that?).

    IE8 is not a browser you have to test for. Instead, it's a browser that's being tested itself. Don't sweat over it : )

    Everything I said about IE8 goes for GooglieChrome as well. Also in Beta.
     
    Stomme poes, Sep 9, 2008 IP
  3. deathshadow

    deathshadow Acclaimed Member

    Messages:
    9,732
    Likes Received:
    1,999
    Best Answers:
    253
    Trophy Points:
    515
    #3
    What Stomme Poes said, double it.

    Do the people in your company not understand what BETA means? If you are finding rendering errors, you need to report those errors to MICROSOFT, NOT fix them in your page.

    Especially if the page renders fine in FF, Opera, Safari and legacy IE versions.

    THAT SAID, there is stuff you should fix on the page. You've got markup errors from a lack of being 'well formed' that are likely hanging the validator before it shows anything else wrong. That Javascripted menu is just MADE of /FAIL/ since it overrelies on javascript, flash and uses a bunch of ID's for no good reason making it bloated AND an accessability headache. You have inlined presentation, your heading orders are nonsensical, you use more than one H1 per page, you have div's wrapping elements for no good reason, that stupid 'clearfix' rubbish, multiple classes on items that don't need classes, comment placement that could break the layout in IE causing whole sections of content to vanish or worse, render twice in different loacations - and that's before we talk all that crap unneeded javascript like mootools. To be honest, I'm suprised it renders properly in FF, much less anywhere else.

    Here's a tip - if you have a 15k of HTML for 1.3k of actual content on the page, something is REALLY wrong, as it's likely two thirds of that document is unneeded/unneccessary bloat. If you need to use 136k of javascript atop that and 47k of CSS for THAT simple a layout?

    Chuck it all, start over from scratch - there's nothing to save here.

    Basically, what you have is a half a megabyte page for something that shouldn't even take a fifth that.
     
    deathshadow, Sep 9, 2008 IP