Home Dashboard Directory Help

Bug Reporting Guidelines


Thank you for taking the time to send us feedback! The effort you make to file great bugs helps us build a better browser for the millions of people who use Internet Explorer (IE) every day.

When we receive bug reports, we try to review them in a timely manner and get them to the engineering team for further investigation. The reality is that not every single bug reported to us is one that we’ll be able to fix. For example, some proposed fixes could violate standards, be too risky for the current release, or break existing sites. There are a few things you can do to help us make the best decision for each bug.

We’ve put together these guidelines to outline the type of information that we find most useful when reviewing bugs. Most importantly, please try to be as complete as possible when you file a bug report. Include sufficient information for us to understand the issue you are seeing, how we can reproduce it, and what impact it may have on Internet Explorer users, web developers, and others who depend on IE being a great browser.

Before Filing a New Bug Report

1.     Ensure you’re running the latest version of IE, since your issue may already have been resolved in a newer version.

2.     Search for existing bugs in Connect to see if your issue has already been reported.

3.     Try to identify specifics steps that would allow us to consistently reproduce the issue you’re seeing, if possible.

4.     Please file separate bug reports for each problem encountered.

Example of a Good Bug Report

 Example of a Good Bug Report

Key Components of a Good Bug Report


A good bug report has a clear and concise title (usually less than 15 words). Summarizing your problem concisely improves our ability to understand and fix bugs.

·         Good: “[IE 11] Unable to type in search box of www.example-url.com

·         Bad: “Search functionality broken”


A good bug report clearly explains what you were expecting to see, and how it differs from what you actually saw happen. We’ve found that both of these perspectives are valuable and help us fix more bugs. For example, describing your expectation can help us fill in gaps and fix bugs that otherwise might not be reproducible, since bugs sometimes depend on external factors like the language of the underlying operating system.

Selecting the correct area

A good bug report has the correct area selected. We want to get your bug report to the right developer as quickly as possible, and selecting the correct area in the form helps.  Since some issues might fall under more than one area, try searching in Connect to find similar bugs in that area. If none of the areas seem suitable, select “Other”—we’ll still investigate J

Precise, reproducible steps

A good bug report is descriptive and easy to follow. A clear step-by-step guide that lets us reproduce a bug is often the single most important factor in determining whether we can fix a bug or not. When we aren’t able to reproduce the bug, it will often be resolved as “Not Repro”. Clearer and more detailed bug reports greatly improve our ability to understand the underlying issues and respond accordingly.

Screenshots & attachments

A good bug report may include screenshots (or even videos). For example, you can use screenshots to guide us through relatively complex steps or to highlight where we need to look to see the issue you’re reporting.

Once again, thank you for everything you do to help us improve Internet Explorer.