Umer Pasha Blogs

Test HTML5 compatibility.

on August 1, 2012

Found this great site to check scores for your browser’s HTML5 compatibility. I use HTML5 extensively these days for mobile apps as well as everyday web programming and layouts. All scores are out of a total of 500. Check out

To keep cross browser compatibility is a great challenge though. Worse offender being Microsoft’s IE. I think it is downright irresponsible that the most used browser in the world comes out with the latest version that scores just 325. Relatively comparing, even my LG TV browser scores 290! It is a disgrace for IE 10!

This also shows why I am always rooting for Google Chrome as the best browser by far on almost any platform. It even beat Apple’s safari and iOS by a fair margin. Down below are the different scores I got for different browsers I have to use everyday to keep cross-browser compatibility issues at bay.

Dolphin HD on Android: 278
Firefox Mobile 14.0.1: 320
Opera Mobile 12.0 : 380
Chrome for Android 18.0: 380

IE 8: 42
IE 9: 143
IE 10: 325
Firefox 12.0: 339
Chrome 20.0: 427

iOS 6.0: 369
Safari 6.0: 384



3 responses to “Test HTML5 compatibility.

  1. Iftikhar Mumtaz says:

    Chrome is the best of the the lot. The only complain I have is its poor text rendering compared to IE and FireFox. Fix that, and Chrome would be perfect.

  2. Umer Pasha says:

    Do you mean the anti-aliasing? You can always force it in CSS:

    -webkit-font-smoothing: antialiased;
    -moz-font-smoothing: antialiased;
    font-smoothing: antialiased;

    It does make it faster to render text though without the anti-aliasing….. and considering the fact that you are only reading for the content 90% of the time on the web and not looking into aesthetics of a website, i’ll take quick over beautiful any day. What do you say?

    • Iftikhar Mumtaz says:

      Not just anti-aliasing, I was talking about ClearType. You can achieve some font smoothing in Chrome using CSS hacks but still the quality of output would be nowhere near IE or FireFox. Anti-aliasing does indeed slow down text rendering but only by a factor that is not humanly noticeable, so the performance hit is negligble. Not sure what’s Google’s rationale behind not implementing proper anti-aliasing in general and ClearType on Windows platform.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: