Note: I'm unable to test the latest preview because I do not have the possibility to test Win 8. I'll check every test when IE10 beta becomes available on Win 7.

credit where credit is due

Note: This table has been updated for Internet Explorer 10 Previews.

This directory contains a lot of testaces for bugs I reported at the IE Connect Database. Some of these bugs were discovered by myself. However, the majority were already published on the web by various people.

Some testcases are completely new, others are extended and some are almost the same as the original testcases.

I apologise to everyone who feels deceived by that fact. Although some of these bugs were already reported in earlier bug collection cycles, Microsoft's policy to close every open bug by the time a new version is released, made it necessary to re-report thise bugs.

Because a lot of bug reports were not re-reported for whatever reason, I decided to report every bug not reported yet by myself. This doesn't include every unreported bug out there, but most of the more (in)famous ones. I ignored most of the original authors to achieve the so called greater goal, i.e. an interoperable web.

I want to thank everyone who ever discovered or reported a bug in any browser. It is you who enable an great web experience to millions of users.

What is a bug?

By 'bug' I mean a problem or unexpected behaviour in Internet Explorer compared to other browsers or compared to a specification. Not all bugs in this list are bugs that document an implementation mistake. Some reports simply describe a different behaviour from other browsers or behaviour that just seems illogical.

How I create a testcase

When I encounter a testcase that works in one browser but not in another one, I try to find out what the bug actually is.

A lot of testcases are very complex - very often too complex. When I found out what the bug is, I try to reproduce it with as little code as possible. That's why some testcases here look almost the same as the original testcase and others are completely different.

Tests rendered in IE7 mode

If accessed from webs.com the testcases may be rendered in IE7 mode because the domain is listed in Microsoft's Compatibility View List. Please make sure the tests are rendered in Standards Mode when viewed (perceivable at the bottom of every testcase by he reported Compat and Document Modes).

External scripts

The testcases are located on a free host webserver that is supported by ads. These are unfortunately added into the testcases. However, before reporting an issue, I test that the testcase on this server works. So there should be no downsides.

Other reports and suggestions

• Implement support for WebM media format (Status: By Design)
• Implement support for APNG image format (Status: Reopened)
• Trying to run DOM Test suites results in blankness (Status: Fixed)
• incorrect media type submitted when uploading png or jpeg images (Status: Fixed)
• Implement the HTML5 parsing algorithm (Status: Ignored)
• HTML documents created through XSLT are rendered in quirks mode (Status: Reproduced)