Slashdot Mirror


Adding CSS3 Support To IE 6, 7 and 8 With CSS3 Pie

rsk writes "Internet Explorer 6, 7 and to some extent 8 have been the bane of every CSS-loving web developer for years. With the spreading adoption of CSS3's fancier rendering effects, like rounded edges, drop shadows and linear gradients, the frustration of needing to deal with IE compatibility is growing. 327 Creative's Jason Johnston has created the CSS3 Pie library to address this. CSS3 Pie adds support for CSS3's most popular rendering techniques to Internet Explorer 6, 7 and 8 by way of the IE-only CSS property 'behavior.' CSS3 Pie is open sourced under the Apache 2 license and can be accessed from its github repository."

6 of 142 comments (clear)

  1. IE? Seriously? by jon42689 · · Score: 4, Insightful

    Honestly, while I realize that there are some people out there using IE, I almost never make it a priority in development. "Oh, it doesn't work? What browser are you using? Internet explorer? Oh, that's the issue then." Why are we trying to fix something that is broken by design and is about as closed as a nun's c**t?

    1. Re:IE? Seriously? by SashaMan · · Score: 4, Insightful

      The fact that this was modded insightful is even more proof of why most tech people should never run a business. "Oh, the majority of users on the internet can't use your site? Tell 'em it's their problem."

  2. Almost never make it a priority in development by Anonymous Coward · · Score: 5, Insightful

    Me either. But on those rare occasions when I'm not developing for unicorns, I have to consider the real world.

    1. Re:Almost never make it a priority in development by man_of_mr_e · · Score: 4, Insightful

      Web developers have this really weird reality perception filter. It's almost like 1984 "doublethink". We have always been at war with Flash, CSS 3 is our friend.

      In Web developerland, whatever the current standard is, has always been the standard, and thus anything that doesn't conform to it is "broken". This ignores the fact that other standards existed before the current standard, and that the meaning of the standards have even changed (CSS2.1 for instance, redefines a great deal of CSS2).

      Granted, IE6 is broken, but not in the way most developers seem to think, or want to claim. It had bugs, and when it was designed, the W3C had not clarified how the box model was supposed to work, and IE6's assumptions were were wrong.

      However, IE6's major failing is simply that it did not evolve. People like to claim IE6 today was intentionally designed to violate standards that didn't even exist when IE6 was created (or were at best ill defined). Mozilla was likewise broken in many such ways, but they evolved and fixed their problems over time. It's like calling a car that requires leaded gasoline "broken" because all you can find is unleaded gas today. It's not broken, it's just out of date.

      Yes, it's frustrating that there is this huge legacy burden on web developers, but please people, stop rewriting history. Stop forming the perception filter that turns you into conspiracy theory spouting retards with no concept of how the web actually was created. (appologies to any real conspiracy theory spouting handi-capable people reading this message, i'm an insensitive clod).

    2. Re:Almost never make it a priority in development by Anonymous Coward · · Score: 5, Insightful

      Sorry, that isn't the reality - its revisionist and misleading. At launch, IE6 did not support the standards in place then. Not close to completely, not correctly (even in places where no interpretation was needed), and where they could interpret - they did so poorly (as you acknowledge).

      Since then, plenty of standards have finalized that were in draft, in wide use, and easily adopted by dozens (yes, dozens) of other browsers. IE did not.

      I was there before IE4. Back when Microsoft was actually trying to keep up. They took a decade off, and IE6 was near the beginning of it.

  3. Re:Pointless. by yoyhed · · Score: 5, Insightful

    This isn't pointless - do you understand what this is? This isn't for people that use IE, it's for people that develop websites for IE. This is a Godsend for me.

    Developing nice-looking websites in Chrome/Firefox/Safari/Opera is easy as PIE (pun intended), but when you want that same site to look good in IE it's a fucking nightmare. This provides some easy ways of making a site look nice in all the major browsers without a huge coding headache.

    --
    WHO NEEDS SHIFT WHEN YOU HAVE CAPSLOCK/ DAMN1