CSS Compatibility updated

I’ve updated the CSS Compatibility Table as the first step in a complete update of all Tables. Frankly, this was one of the more boring updates I’ve ever done.

I tested four browsers:

All in all a meager result for many hours of work. I suppose I should be extatic about how little browsers do wrong these days, but it makes my work considerably more boring.

Further updates are planned, but I’m not going to give a specific timeline for them; we’ll see how it goes.

This is the blog of Peter-Paul Koch, web developer, consultant, and trainer. You can also follow him on Twitter or Mastodon.
Atom RSS

If you like this blog, why not donate a little bit of money to help me pay my bills?



Comments are closed.

1 Posted by Alice on 11 November 2008 | Permalink

Thank you for doing this kind of work. Its good to know this stuff.

2 Posted by Vasil Rangelov on 11 November 2008 | Permalink

"IE8-as-IE7 (in backward compatibility mode, in other words). There are no differences with a regular IE7. "

That's great news. It means we can REALLY rely on this mode to test web pages as they would appear in IE7.

I can see it now - the MSIE team bragging about this: "Independant researchers (like PPK[link]) confirm this mode as a reliable way to test IE7 inside IE8".


3 Posted by David Bloom on 11 November 2008 | Permalink

Can't you test ::selection on iPhone 3G using...
var r = document.createRange();

4 Posted by ppk on 11 November 2008 | Permalink

Vasil, let's wait for the JavaScript tests before handing a final verdict. But I must admit it's looking good now.

5 Posted by David Håsäther on 11 November 2008 | Permalink

One small addition: Opera supports text-overflow with "-o-"-prefix.

6 Posted by ppk on 11 November 2008 | Permalink

Thanks David, added.

7 Posted by Harley Jones on 11 November 2008 | Permalink

If you want to work on something that has plenty of browser incompatibilities and non-standard behaviors, can you look at JavaScript exception handling?

Things like:
1. window.onerror (IE and Gecko only, I think)
2. document.onerror (Opera only, I think)
3. <IMG onerror>
4. <SCRIPT onerror>
5. the Error object

I mean, I'd hate for you to have nothing to do :)

And by the way, thanks for taking the time to do all that you already do.

8 Posted by Gavin on 12 November 2008 | Permalink

from http://www.css3.info/css3-support-in-firefox-31/ it's said a lot of new CSS features are supported, have you tested them yet?

9 Posted by pd on 13 November 2008 | Permalink

Invaluable work, sorry it bores you but I think that's a good thing.

Can't wait to see the latest JS compatiblity. I expect that will be more 'interesting' for you.

If it's that difficult and boring to do these tests, perhaps you could look at distributing the load?

I'd be happy to help.

10 Posted by Stomme poes on 13 November 2008 | Permalink

I've noticed something with the + adjacent sibling selector and Safari-Chrome vs all the other browsers who support it. I need to make another test, but while in IE7, FF2/3, Opera and Konqueror you can say sibling:hover+sibling child {styles;}, in Safari-Chrome so far I can only reference the sibling itself but none of its own children: sibling+sibling {styles;}. I need to read the specs to see who's right or if it's just left open, but it's interesting.

11 Posted by Ed on 13 November 2008 | Permalink

Now that you've opened the can of worms of testing pre-release software, please consider testing a recent WebKit Nightly.

12 Posted by Barney on 23 November 2008 | Permalink

Chrome does support text-shadow, but its anti-aliasing breaks and the alpha gets rendered as white. The same effect is visible when a PNG featuring alpha-channel pixels is given a CSS opacity of less than 1.