Slashdot Mirror

← Back to Stories (view on slashdot.org)

CSS Support Could Be IE7's Weakest Link

Posted by Zonk on from the who-uses-that-css-stuff-anyway? dept.

Ritalin16 writes "Many web developers may be disappointed to hear that Microsoft decided to hold off on full CSS2 support with IE 7.0. As said by Microsoft-Watch: 'One partner said that Microsoft considers CSS2 to be a flawed standard and that the company is waiting for a later point release, such as CSS2.1 or CSS3, before throwing its complete support behind it.'" More commentary available from ZDNet. Generally related to the IE 7 Acid Test thrown down by Opera.

7 of 575 comments (clear)

  1. So... by Anonymous Coward · · Score: 5, Insightful

    Support CSS 2.1. We're really not picky. Anything is better than nothing.

    1. Re:So... by Moonshadow · · Score: 5, Insightful

      CSS2 has some flaws, but it's a far cry better than anything IE currently offers. Writing cross-browser CSS can be an exercise in frustration unless you resort to browser-specific stylesheets. I just want IE to support, you know, the standard.

  2. Just like... by turtled · · Score: 5, Insightful

    See, that's the problem. It's just like Microsoft to say "We'll wait til later ( point release, such as CSS2.1 or CSS3) before throwing our complete support behind it" I don't understand! You have to plan for the future, no plan after the fact!

    --
    "I cannot think of any need in childhood as strong as the need for a father's protection." -- Sigmund Freud
  3. This is silly... by Anonymous Coward · · Score: 5, Insightful

    Yesterday I had to make a page.
    I made it in firefox with no problems. Then, I looked at it in IE and it was terrible. If I code to standards why can't microsoft make their products support standards?

  4. At this point, who cares? by Ars-Fartsica · · Score: 5, Insightful

    People will use IE7 because windows update will automatically put it in place of IE6 one day. It will fix some bugs and create others. It will not change how web developers create sites, it will not derail Firefox, it will not make people salivate for Longhorn.

  5. Re:Why I hate developing webpages... by tepples · · Score: 5, Insightful

    Designing pages for one particular Web browser is a bad idea

    Using CSS2 and designing for the set of all browsers known to support most of CSS2 isn't "designing pages for one particular Web browser".

  6. Well, hey Microsoft -- I say F*CK YOU right back by l0ungeb0y · · Score: 5, Insightful

    I've decided that from here on out I will invoice my CSS time for IE seperately. Being that I create most browser interfaces in XHTML and all layout is 100% CSS, I will now isolate the huge chunk of time I must spend on each project for IE compatability. I will also make it clear UPFRONT by making an accountance in my proposol for just how my design time will be devided up and how much time I estimate to spend on IE compatability vs supporting the rest of the world.

    Why single IE out on my invoices and proposols? To let companies know where that extra $2,000.00 went for 20-30 hours of my time. That's why. And in hopes that they will opt not to engage in that expenditure.

    I'd urge all other UI designers and developers to do the same.
    And if the client decides that they wish not to support IE, a small victory shall have been won.

    It was fine 5-6 years ago to say "Ooops -- you're using that Netscape piece of shit, please come back using a real browser"
    I say it's time we start doing this again, but for IE and for the exact same reasons.