Google Chrome Frame

• Enable open web technologies in Internet Explorer
  Google Chrome Frame is an open source plug-in that seamlessly brings Google Chrome's open web technologies and speedy JavaScript engine to Internet Explorer. With Google Chrome Frame, you can:
  
  • Start using open web technologies - like the HTML5 canvas tag - right away, even technologies that aren't yet supported in Internet Explorer 6, 7, 8, or 9.
  • Take advantage of JavaScript performance improvements to make your apps faster and more responsive.
• Get started with Google Chrome Frame
  Enabling Google Chrome Frame is simple. For most web pages, all you have to do is add a single tag to your pages and detect whether your users have installed Google Chrome Frame.
  
  • If Google Chrome Frame is not installed, you can direct your users to an installation page.
  • If Google Chrome Frame is installed, it detects the tag you added and works automatically.

http://code.google.com/chrome/chromeframe/

Respond.js

A fast & lightweight polyfill for min/max-width CSS3 Media Queries (for IE 6-8, and more)

• Copyright 2011: Scott Jehl, scottjehl.com
• Dual licensed under the MIT or GPL Version 2 licenses.

The goal of this script is to provide a fast and lightweight (3kb minified / 1kb gzipped) script to enable responsive web designs in browsers that don't support CSS3 Media Queries - in particular, Internet Explorer 8 and under. It's written in such a way that it will probably patch support for other non-supporting browsers as well (more information on that soon).
If you're unfamiliar with the concepts surrounding Responsive Web Design, you can read up here and also here
Demo page (the colors change to show media queries working)

https://github.com/scottjehl/Respond

html5shiv

Public repo for the latest HTML5 JavaScript shim for IE to recognise and style the HTML5 elements.
Source code adds new HTML5 elements (which is simple code), but actually mirror's @jon_neal's and afarkas's IE Print Protector project. It's currently up to date, and for the full details and uncompressed source code see here: http://www.iecss.com/print-protector/
Seriously, these guys did all the hard work - getting it to work in the browser was easy, @jon_neal and afarkas made IE actually print HTML5 elements. Please take a moment to thank them!

http://code.google.com/p/html5shiv/

Diagnose and Prevent AJAX Performance Issues!

AJAX improves user experience by moving more code to the browser. Frameworks accelerate development, but lead to opaque application behavior and new performance issues.
dynaTrace AJAX Edition aims to solve these issues:

• Understand performance as real users experience it
• Differentiate between browser or server bottlenecks
• Trace asynchronous JavaScript executions for the full round-trip
• Analyze JavaScript, AJAX remoting, network and rendering performance in real-time
• Save performance data for interactive offline analysis
• Transform Selenium/Watir tests into performance tests and integrate them with your CI environment

http://ejohn.org/blog/deep-tracing-of-internet-explorer/
http://ajax.dynatrace.com/pages/

Ultimate IE6 Cheatsheet: How To Fix 25+ Internet Explorer 6 Bugs

Written by Benjamin / September 15, 2009

The best strategy for dealing with Internet Explorer 6 is not to support it.

Stop. Ok, I feel your frustration. You're a web developer and you're ready to tear your hair out because you have to support Internet Explorer 6, but, to put it tactfully, IE6 doesn't support you. You've spent hours on it, but you just can't seem to get your layout right. I can empathize. I can also help.

This isn't one of those rants about IE6 or a campaign to try to kill it. There are enough of those around the web, but they don't help if you need to support IE6 because it still has a significant enough marketshare that you can't ignore it for business reasons. No, this is the resource you've been hoping for.

I've scoured the web for resources and also included some of my own fixes for IE6 and now I've put it all together in this cheetsheet/reference manual as a resource for anyone who has to deal with Internet Explorer 6. Where possible, I've done my best to provide the cleanest and valid solutions to each bug instead of ugly hacks. I've also tried to give proper credit for each case, but some of the solutions have been shared so many times that finding the original discover of each fix is difficult. If you see a missing credit or if I missed a bug and fix, please contact me and let me know and I'll update this page.

This massive IE6 guide took a while to put together, so bookmark it, share it, tweet it, and use it to save yourself and your coworkers hours of screaming at your monitor and banging your head against your desk or other inanimate objects. Don't be fooled, however, this cheatsheet is as much for me as it is for you.

http://www.virtuosimedia.com/tutorials/ultimate-ie6-cheatsheet-how-to-fix-25-internet-explorer-6-bugs

Eazy IE6 PNG fix

http://www.nikibrown.com/designoblog/2009/08/21/eas-ie6-png-fix/

MHTML - when you need data: URIs in IE7 and under

MHTML is MIME HTML, or if you insist on me spelling it out completely is like "Multipurpose Internet Mail Extensions HyperText Markup Language". In short it's HTML but like email with attachments. In one "multipart" email you can have several... hm, things - HTML version of the email, text-only version, attachment, another attachment...

MHTML is the same but for HTML. In one file you put a bunch of stuff (e.g. image files) and you save on the precious HTTP requests.

http://www.phpied.com/mhtml-when-you-need-data-uris-in-ie7-and-under/

Introducing IE=EmulateIE7

Bill Gates’ recent Tech Ed keynote and Tony Chor’s follow-up blog announced that IE8 Beta 2 will be available in August in many languages. We are encouraging sites to get ready for Beta 2 prior to release as it will present a big jump in IE8 browsing traffic.

What does “getting ready for IE8” mean for web sites? IE8 displays content in IE8 Standards mode – its most standards-compliant layout mode – by default. In previous blog posts, we’ve discussed how this aligns with our commitment to Web standards interoperability. However, browsing with this default setting may cause content written for previous versions of IE to display differently than intended. This creates a “get ready” call to action for site owners to ensure their content will continue to display seamlessly in IE8.

The preferred response to this call to action is to update the site to ensure that IE8 is provided with standards content fitting the DOCTYPE. However, we know it is very important to give site owners the chance to update site content on their schedule without affecting user experience. As such, we provide a meta-tag that tells IE8 to display an entire site or a specific page like it did in IE7.

In IE8 Beta 1, that option is the “IE=7” X-UA-Compatible tag, which instructs IE8 to display content in IE7 Standards mode. However, the scenario this doesn’t address is when IE=7 is applied as an HTTP header to a site that contains Quirks mode pages. The IE=7 HTTP header will force all pages – both Quirks and Standards – to display in IE7 Standards mode. Developers using this header while updating their sites would then have to add the “IE=5” tag to each page they want to keep in Quirks mode. This logic is fine for many websites. However, if a site has lots of Quirks mode pages, or for the case where pages with frames host a mix of Strict and Quirks mode content – as brought to light by IE8 Beta 1 user feedback – the compatibility opt-out adds a bit more work than we intended.

In response to the great IE8 Beta 1 feedback we’ve received so far, we are introducing the “IE=EmulateIE7” tag to address this problem. EmulateIE7 tells IE8 to display standards DOCTYPEs in IE7 Standards mode, and Quirks DOCTYPEs in Quirks mode. We believe this will be the preferred IE7 compatibility mode for most cases. Support for IE=EmulateIE7 is available now as part of the IE June Security Update for IE8 Beta 1. Installing this update will enable you to verify you’ve applied the EmulateIE7 tag to your site correctly.

In summary, IE7 compatibility support looks as follows:

Content Value	Details
IE=7	Display in IE7 Standards mode; Already supported in the IE8 Beta 1 release
IE=EmulateIE7	Display standards DOCTYPEs in IE7 Standards mode; Display quirks DOCTYPEs in Quirks mode; Available through the IE June Security Update for IE8 Beta 1

There are two ways to implement this tag:

• On a per-site basis, add a custom HTTP header

X-UA-Compatible: IE=EmulateIE7

• On a per-page basis, add a special HTML tag to each document, right after the tag

<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />

Implementing the HTTP header is beneficial if a site owner wants most of their site to render as it did in IE7 or if there are no plans to update site content. Inclusion of this header honors any Quirks mode pages that belong to the site.

Using the meta-tag on a per-page basis is beneficial when the publisher wants to opt-in specific pages to render as they did in IE7.

NOTE: The X-UA-Compatible tag and header override any existing DOCTYPE. Also, the mode specified by the page takes precedent over the HTTP header. For example, you could add the EmulateIE7 HTTP header to a site, and set specific pages to display in IE8 mode (by using the meta-tag with content=”IE8”).

Using the IE=EmulateIE7 compatibility tag is a simple way for users to continue their current experience when browsing your site until you can update with more standards-compliant content. Although adding this tag will prevent most display issues, you may also need to update your site to properly detect IE8. To learn more about IE8 document compatibility and browser detection, check out the IE Compatibility Center.

http://blogs.msdn.com/ie/archive/2008/06/10/introducing-ie-emulateie7.aspx

IE NetRenderer

IE NetRenderer allows you to check how a website is rendered by Internet Explorer 7, 6 or 5.5, as seen from a high speed datacenter located in Germany. Just type in a URL in the field above and try it out - it's free!

New: We have updated the IE8 Beta 2 engine to Internet Explorer 8 RC1.

Unlike other screenshot services, we are able to process a large number of capturing jobs in parallel and in realtime, making it the fastest service that we know of.

This web rendering tool is ideally suited for web designers working on Apple iMac and Linux workstations. It allows to verify web designs natively on all popular Internet Explorer versions, without the need to set aside several physical or virtual Microsoft Windows PCs just for that purpose.

http://ipinfo.info/netrenderer

Companion.JS

Companion.JS (pronounced Companion dot JS or CJS) is a Javascript debugger for IE. The current version is 0.4.2.
Companion.JS adds the following features to IE :

• Detailled javascript error reporting (call stack and real file name where the error occured).
• "Firebug"-like Console API feature.
• Javascript console feature useful to inspect javascript objects at runtime.
• A toolbar icon to open the Companion.JS panel.

To be able to use Companion.JS you'll also need to install Microsoft Script Debugger. See Installing Companion.JS for details.



http://www.my-debugbar.com/wiki/CompanionJS/HomePage