Safari with the best CSS3 support, IE ruining it for everyone again

Once in a while I go read up on CSS3, then I get frustrated that it’s not a standard yet because it’s so great.

Today I decided to run CSS3.info’s selectors compatibility test. Not that I needed confirmation but, obviously, the (still large), installed base of IE6 around the world is mucking things up for everybody else.

The test is here: http://www.css3.info/selectors-test/test.html

Safari (3.1.2), performed the best passing all the tests. Firefox (3.0), a bit to my surprise – it being so recent and all – only supported 36 of the 43 selectors tested but it was Internet Explorer 6, which I tested because it’s still the standard installed browser on workstations at where I work passed only 10 of the 43 selectors tested.

And, get this, it passed all the #id tests but it failed one of the .class tests! IE6 doesn’t even fully support .class which is the basic CSS selector.

I’d still like to test IE7 and Opera, but I don’t have them right now. I’ll check later and update.

In the meanwhile, we’d better sit down, if we’re waiting for CSS3 to “come out”.

6 thoughts on “Safari with the best CSS3 support, IE ruining it for everyone again

  1. Wait. You are criticizing a browser that was launched in 2001 !?! And comparing it to browsers launched 7 years later? If you tested with the latest versions of both Safari and FF you should use IE8. A great browser.

    Sometime people are just too biased with their anti-MS mindset. Puhf :-(

  2. Did you read what I wrote?

    The problem is not IE6 itself, it’s the fact that it’s still being installed by IT departments the world-over.

    Because it was so buggy but prevalent, people built web-apps around it and now they can’t get rid of it.

    In my company, if you update the workstations to IE8 the employees will lose access to the corporate portal and be unable to schedule vacations or manage their expenses.

    So because IE6 forced people to get stuck in time, no one else can move forward.

  3. MM, using IE8 wouldn’t help much either… :) they’re not putting their feet on CSS3… albeit, much better, it’s not as advanced as its competitors. Also, not all companies have the same audience as 37 Signals. Bryan Veloso has also dropped support for IE, but that’s because he can. You should know that you can’t force the hand of your users to update the browser… that’s like returning to “This webpage only works in IE.”, only the opposite.

    Pedro, Opera 9.5 (when it was still in beta) was the first one to pass all the selector tests. Pretty cool stuff. (this was back in sept 2007 http://flickr.com/photos/andr3/1344239312/ )

    It’s too bad that people don’t update their browsers, but designers can always opt for progressive enhancement. That’s what I’ve tried to do with the layout of my blog. It’s a test-case (fugly as hell, but that’s my fault), and it shows differently on every browsers, still maintaining the functionality… everything works, they just don’t look the same.
    Granted, it’s not that pretty, or as pretty as more elabored graphic designs, but the concept is there. Can be worked on.

    Stuff like border-radius, text-shadow, etc. are only available in certain browsers, but that doesn’t mean you can’t use then.. it just means not everyone will see them. Also, not everything on css3 has been closed, so could happen, that before the final version of the spec, webkit will have to rewrite some of their stuff. hehe That would ironic. :)

  4. MM, yes, it’s the companies fault, to a degree, but IE6 is, above all, a bad product. “Revolutionary” doesn’t exactly describe it as well as “flawed”.

    It got people stuck on bad web standards, or actually, no standards at all.

    I still hear people saying that browser X sucks because they can’t do their supermarket online shopping on it, and IE6 rules because it works. Obviously the problem is that the supermarket’s website was built around non-standard IE6 bullsh*t and now isn’t supported by other browsers.

    So, to a degree, IE6 is to blame for badly built websites.

    Also, 37 Signals as an example? Not very good, really. I don’t think most common users even know 37 Signals, the same way they can’t distinguish between a badly built website and a bad browser.

    André, the last time a redesigned my blog I decided not to care about IE6, and then I looked at the numbers… :-(

    Despite it being old as hell, people are still massively using it.

    I am planning a new, simpler design that works everywhere. I will definitely look at what you’ve done for inspiration.

Leave a Reply