Dealing with Internet Explorer in your JavaScript Code

It’s almost the end of 2008, and thanks to the hard work of web standardistas, browser vendors, and JavaScript framework developers, cross-browser JavaScript code is much less of an issue than it used to be. Even Microsoft is feeling the love — the upcoming Internet Explorer 8 will be a (mostly) clean break from legacy Internet Explorer releases and will behave much more like Firefox, Safari (WebKit) and Opera. …And they rejoiced.

So why is it that when I look under the hood of some recently produced web pages (learning management systems, courses produced by e-learning rapid development tools, general web pages, etc.), the pages’ JavaScript often includes incredibly out-of-date and bad-practice Internet Explorer detection?

Here’s a quick rundown on the dos and don’ts.

MooTools 1.2 & Opera 9.5 released, FF3 coming soon

Some quick development news: MooTools 1.2 has finally been released. MooTools is really great, I hope more people start using it. Firefox 3 should be officially released this Tuesday (June 17). Party on. Oh, while I’m at it, I guess I should mention Opera 9.5 was just released, too. I’m not a big Opera fan, but v9.5 includes some important advances in CSS3 support, which hopefully will help other browser developers to make some progress with their own CSS3 implementations.

Scroll to Top