Skip to main content


Browsers that use modern operating systems more directly deliver better experiences. Browsers that compromise (by spreading across too many OSes and OS versions) face challenges.

We can't decide if we want IE to drive Windows adoption or Windows to drive IE adoption.

The best HTML5 is native to the operating system, so Web sites have the fewest translation layers to pass through.

The browser is part of the OS. The browser has always been part of the OS. We have always been at war with Eastasia.

Native HTML5 support in Windows with IE9 makes a huge difference in what sites can do.

We're really, really sorry about IE6. Not sorry enough to disable Windows activation and allow all the software pirates in China to upgrade, but sorry nonetheless.

Web sites and HTML5 run best when they run natively, on a browser optimized for the operating system on your device.

I think we can all agree to hate XUL.

We're about three weeks into development of IE10, and based on the progress we've made, we want to start engaging the development community now.

Imagine how much progress we could have made if we hadn't ignored the web for ten fucking years.

Native HTML5 ... native HTML5 ... run natively ... most native ... only native ... native graphics ... native ... Native HTML5 ... Native HTML5 ... native and robust ... native applications ... Native implementations ... non-native ... native HTML5 ... native ...

I am high as a kite.

When this post was initially published, I forgot to include the onerror event handler for the HTML5 video element. This caused the video to not play in browsers that don't support MP4/H.264 video. That has been corrected.

The irony of using the phrase "same markup" nine times while delivering different markup to other browsers is entirely lost on me.

The only native experience of the Web and HTML5 today is on Windows 7 with IE9.

We would like HTML5 better if it were spelled "ActiveX."