IE Feedback: Looking Back, Forging Ahead

IE9 users significantly impacted the engineering process and product with high quality,
high value feedback. It is for this reason that we are pleased to announce that
the Internet Explorer Feedback Program will remain open on an ongoing basis. Users
continue to be able to search, reactivate, or log new bugs on
, and the IE team will continue to investigate and resolve them.

We would like to reiterate our
deep appreciation and thanks
for the time and effort our users invested
in helping us to make a better product. We provided the specifics on the huge impact
of feedback in our


– in this post we’ll take a last look at the feedback data
from IE9 and discuss the ongoing process as we look ahead to the next release.

The Numbers

For the Beta, we received over 17,000 bugs. The earlier Platform Previews and the
RC added over 6,000 more pieces of feedback to that, resulting in 23,376 pre-release
bugs logged on Connect in almost exactly
1 year. When you add to this the over 21,000 comments and 8,000 validations, we
received over 52,000 pieces of feedback from over 10,000 users. This is a huge response,
and we are both proud to have attracted such interest and thankful for the support
of our community. If every user spent just 2 minutes to find an issue, search for
a bug, and then either create a new bug, validate the existing bug, or comment on
it, you’d end up with over 200 business days of engineering assistance to the IE


When we launched the
IE8 feedback process
, we talked about the overwhelming response of the public
IE7 feedback program leading us to introduce an invitation-only program. As we discussed
when we launched the public
IE9 Platform Preview Feedback
program, the
expressed in the
were clear on that decision for IE8. For IE7, the public
feedback program generated 10,905 bugs over roughly 16 months, or 681 bugs per month;
it was 1,948 bugs per month for IE9, almost triple the volume. We knew that with
a more connected world, frequent Platform Preview releases, and by making it easier
to log bugs using the Send Feedback Tool we’d receive significantly more bugs than
ever before, but we also knew that only through great feedback would we be able
to deliver a browser that met our customers’ needs.

Maintaining the Feedback Loop

When we started IE8 and over the course of IE9, users

over the lack of continuity in feedback loop. With the
start of IE9 we remedied the problem with losing bugs against previous releases
– you now can search across both IE8 and IE9 for bugs. As we wrap up IE9, it is
because we know that great feedback makes a great product that the Internet Explorer
Feedback Program will remain open. Users can go to
to log bugs against IE9 RTM, and we will triage these bugs and resolve
them as they are addressed in future releases of Internet Explorer. As before, we
ask that developers and consumers provide us feedback on the Web platform and the
user experience of IE9:

  • Do the new capabilities (HTML5, Tracking Protection Lists, etc) function as we’ve
    described them?
  • Do they do what you’d expect?
  • Do you experience reliability or performance issues when using any of them?

At the same time, now that we have released the final version of IE9, we are no
longer accepting bugs logged against the Beta or Release Candidate. We ask that
users install the IE9 RTM, retry their
scenario, and reactivate their bug in Connect
if it is still an issue.

Wrapping up IE9

While we review and prioritize your incoming RTM bug reports, we will continue to
close down pre-release IE9 feedback. We will be looking at the bugs you have reactivated,
the final bugs that came in over the last week of the RC, and the bugs where you
have added comments or validations after the release of the RTM. Just as we committed
to when we talked about
Product Feedback Systems
, every single bug will be reviewed and we will keep
you informed as they are addressed.

Thanks again for your feedback on IE9!

—Justin Saint Clair, Program Manager, Internet Explorer

Comments (21)
  1. alvatrus says:

    Why are you closing the IE9 bug reports? Because that is a lot of effort going down the drain.

    You put the onus on the community to review and reactivate the data in *your* bug-tracking system.

    I can somehow understand you want to start from a clean sheet, but this won't endear you to the people you just gave a lig "Thank you."

  2. As stated a Million Times already says:

    You can only CLOSE a bug when a FINAL resolution has been made.  The valid options are:

    a.) CLOSED – This is a duplicate of {add link to bug ###}

    b.) CLOSED – This will never be "fixed", it is not a bug, it is a feature {link to article, spec, blog post that describes WHY an unexpected behavior is taking place}

    c.) CLOSED – This was FIXED in version/release X

    d.) CLOSED – This bug is not reproducible

    e.) CLOSED – This is not a valid bug report.  If you still feel there is an issue please expand your bug report with full details of how the bug can be reproduced

    You may NOT CLOSE a bug because you hopefully, maybe one day plan to address this in a future release.  Feel free to "SUSPEND" the bug, "POSTPONE", etc. but DO NOT CLOSE it! It is NOT RESOLVED.

    This is why developers are very frustrated about Connect because it isn't run like a proper bug tracker.

    Bugs can only be CLOSED if the issue is in some way shape or form RESOLVED.

  3. Peter says:

    When you fix a bug in IE9 RTM, how will users get the fixes? Will they be included in the next monthly security update? As it seems, there won't be an IE 9.01 (I still remember IE 4.01 and 5.01) that would contain all the fixes for IE9 RTM…

  4. hdmi says:

    Helping a remote user who picked up some nasty Vista malware.  It's blocking me from getting to any other browser's websites do that I can download them.  Guess it loves IE an awful lot.

  5. benedicht says:

    My wishlist, and feedback:

    -Sessions for tabs('Reopen last session' is not a valid option in 2011)

    -Blank(ugly) titlebar, you can make more place for the real web content if you place something there(tabs and/or address bar)

    -Customizable hotkeys, and gui

    -Why the browser's options are in the 'Internet Options'?

    -More tab options. (I want new tabs open next to the current one.)

    -Rethink the extension system: easier development, more options for the developers, autoupdating them, etc.

    -User (java)scripts.

    -Syncronization of the history, faworits, etc. between IEs(home and work pc, IE on mobile with WP7).


    These are not new features on other browsers! If the IE team wants me, then i want more than a fast browser engine.

    The platform previews are not less comfortable than the final release of IE9…

  6. Aethec says:

    I think you should use one of those websites where you can post your ideas and everyone has X votes to use on promoting ideas they like.

  7. xpclient says:

    There was no need to deliberately cut off Vista support without giving any technical reason as right now Vista is in mainstream support. Even IE8 RTMed in March 2009, and XP mainstream support ended just a month later in April 2009. Microsoft could have done the same for Vista and release IE10 in March 2012 because Vista mainstream support ends in April 2012. Web developers have to do the added work of supporting IE7,8 on XP/Vista, IE9 on Vista and IE10 on Windows 7 and so on. With other browsers, multiple versions is not a problem because the rendering does not break with newer versions or doesn't require compatibility view meta tags or version specific hacks. IE remains the only browser that is more concerned with pushing Windows more than helping web developers.

  8. EinmalIM says:

    Please add an option to disable font smoothing and/or sub pixel positioning. My eyes cannot stand the unsharp blurry text and that stops me from upgrading to IE9.

  9. You Don't Just Throw Away Bugs says:

    I am one of the active Microsoft Connect users during the Internet Explorer 9 Beta.

    I have watched several bugs being Force-Closed than fixed.

    Kinds of make you think that filing bugs in Microsoft Connect is not worth the effort anymore.

  10. Microsoft Connect VS BugZilla says:

    In BugZilla, a fix to a bug can be deferred, and can be marked as such.

    In Microsoft Connect, many bugs are marked as "As Designed".

  11. IE9Fan says:

    Please add an option to "pin" most visited sites on the new tab page. That way when browsing history is cleared, those pinned sites remain.

  12. As Designed is NOT the same as Deferred says:

    Lets be extremely clear. As noted above, "As Designed" is a special status that means it was INTENTIONALLY DESIGNED a certain way ON PURPOSE and will not be changed because it was done this way for security, usability, or whatever.

    Unfortunately Microsoft has no clue how to use the "As Designed" status and slaps it on anything they don't want to do or deal with right now. — this is the problem!!!!!

    Without a "Deferred" status you are absolutely marking the status of some bugs incorrectly.

    Like everyone else that ditched Connect due to the unbelievably bad management/design of the tool I don't plan to return anytime soon.  However if Microsoft plans to fix Connect, add a Deferred status and update the bugs and reply to comments on a frequent basis I'd be more than happy to return.

    If I return and see a single "100% reproduce-able, well documented bug in IE" marked as "By Design" again I can assure I will never, ever return to Connect again – Microsoft has cried wolf with Connect 3 times already – we will not stand for a 4th.


  13. Quppa says:

    Great, but can you get in touch with the Connect team and tell them to ease up on the AJAX? Having the navigation view reset every time one clicks 'Back' or 'Refresh' is supremely annoying.

  14. hAl says:

    The connect site is extremely poor performing and anoying to use so I don't use it anymore.

    Almost like that for the blog here which is also extremely poor software.

  15. Fake Al Gore says:

    IE9 is so close to being my preferred browser except for the lack of extensions. There is no good (stable) AdBlock Plus-type feature. I can't install the Reddit Enhancement Suite. I can't install GreaseMonkey or their scripts. These are things that work in multiple other browsers. Why won't the IE team create a new extension interface that will allow these sorts of amazing enhancements to functionality?

  16. pmbAustin says:

    My biggest UI beef of the moment:  I have a dark background/wallpaper.  Thanks to the transparent/translucent tabs, I can barely read anything on them.  In IE8, the tabs were solid.  Please make a new update that makes the background behind the tabs SOLID (especially when they're on a line by themselves).  Also, the active tab is STILL difficult to see in many cases.  And sometimes the colored tab groupings are way too close in color to the default tab color, making grouping difficult to discern.  And finally, the 'close' box… I know a lot of people asked to be able to close a tab without switching to it, but I've accidentally closed so many tabs right now that I find that feature more of a nusance than the old behavior.

    And I'm still finding way too many sites that don't function under IE9. recently had a survey, and none of the survey controls worked.  And local real estate pages have 'slide shows' that simply don't function.  Even under compatibility mode.  They work just fine in other browsers.  So that's frustrating.

  17. Gérard Talbot says:

    @Justin Saint Clair [MSFT]

    In the last 5 years, a lot of people have been consistently complaining with regards to the way bugs are closed, resolved during beta development, making them waste time, efforts, typing to re-file, resubmit the same bug reports again when the next development phase starts. It's been like that since IE7 development. Other bug tracking systems used by other browser manufacturers use keywords field (eg needreduction, testcase), component field, target field, etc. use better resolution reserved words (latered, futured, fixed, worksforme, duplicate, etc), etc,etc. I explained clearly and cleanly in the past how this IE beta feedback could have been improved.

    > Users continue to be able to search

    > you now can search across both IE8 and IE9 for bugs

    What you say is incomplete. It is not possible to view a bug report (even if you're the original reporter) or search bug reports without registering and then logging in into connect IE beta feedback. No one has to do this with other browser manufacturers' bug tracking systems (except Opera BTS).

    Microsoft changed this after IE8 beta development without any explanations, justifications.


    > The connect site is extremely poor performing and anoying to use

    Years ago, I said so in this blog and I was not alone; suggested improvements in good faith were given too.

    > the blog here which is also extremely poor software

    The blog software has most likely only been tested for IE. I wrote about it and nothing improved.

    Eg. This blog does not have a preview feature; a simple thing that others already reported years ago.

    "Why can't this blog work like other blogs and have markup and preview."…/the-first-year-of-ie7.aspx

    Gérard Talbot

  18. @hAl:

    > The connect site is extremely poor performing and anoying to use so I don't use it anymore.

    Have you reported the issue directly here: You can see how they would respond to it then.

  19. hAl says:


    No, I don't, I am pretty sure everyone working at MS using connect knows the connect software is crappy and similar for the MSDN and Technet blog software.

  20. @Microsoft Connect VS BugZilla says:

    you are right what you expect from IE. they show you madness by showing their thing and thought everywhere.

    like in IE video someone joke on Chrome and firefox because they have something. can you believe joke on thing who have something insead of have something not prove which type of mind they have. well can you show me how much time developer get frustrated from chrome or Firefox prehaps their is much developer who make their application in chrome and firefox and only test in IE. because who not know IE6.

    IE9 is undoubtly have performance but can anyone tell me how much time someone got problem in firefox and chrome. prehaps in firefox and chrome extension have easily avilable to make experience better so their is nothing anyone feel in chrome they not have. when someone move from chrome to IE their is not single problem they have they have much thing they feel they not have.

    1. extension addons personas like customization

    2.  instant integration with web application  [ minus point of IE] because their is much person on internet have facebook or twitter account and many of application have addons in chrome and firefox to work easily with them.

    i thing someone from IE can make a big list then me for both products' pros and cons if they write trough free mind not by  think only one side thought.

  21. guttersnipe says:

    since upgrading to ie 9, i have switched to google chrome and safari. Reason, take a reasonably good browser, speed it up a bit, change the way it looks, add some junk that no one needs, make the 64 bit version unusable, AND MAKE IT CRASH CONSTANTLY.  Result. another user bites the dust and moves to something more reliable. i am probably wrong in my assumptions but don't have the time to wait on pages not loading, and being told that flash does not support this application. Fancy tricks and all singing all dancing applications, why. all i want is to type in what i want to look at and save some pages to bookmarker for using again, and thats it. MAKE IT SIMPLE. P L E A S E!!!!!!!!!

Comments are closed.

Skip to main content