Get flash to fully experience Pearltrees
In a perfect world, cross-browser testing would be straightforward. We would download a legacy version of a browser, run it, and be able to instantly test our pages and scripts without a single care in the world. The reality of cross-browser testing, though, is very different. Issues such as runtime conflicts when running multiple versions of the same browser and inaccurate third-party testing tools mean we can spend hours just evaluating whether a testing set-up is anywhere near reliable. I’m a user-interface developer at AOL (yes, we’re not dead yet!), and in this multi-part post I’ll take you through the exact set-up we use to accurately test content that will be potentially viewed by up to millions of users with a very diverse set of browsers.
Internet Explorer, this current pain in the… code for designers nowadays, had its days of glory a long time ago, when IE6 was launched, cause at that time, believe it or not, IE6 was a top notch browser. With time, things have changed and changed dramatically, Internet Explorer having to face an incredible load of hate directed to itself, especially coming from web designers and developers. Not even the release of IE7, IE8 or even IE9 didn’t make much of a difference cause every time a new version came, it was still behind with the existing web technology. Other browsers have problems too with certain features, but Internet Explorer bites the dust when it’s compared with any other serious browser, you just have to name it Firefox, Safari, Chrome or Opera.