IE7 Is Coming This Month…Are you Ready?

The final release of IE7 is fast approaching … and I mean really fast … and will be delivered to customers via Automatic Updates a few weeks after it’s available for download. We want to ensure that you are ready and the information below will help get you there.

Compatibility with sites, extensions and applications has been a very high priority for us as we develop new features, enhance the existing features and move the platform forward to be more secure and standards compliant.  We are continually listening to feedback from our customers, partners and leaders in the industry to resolve major compatibility issues to ensure our common customers have a great experience with IE7. As we make key improvements in areas such as layout and security, some changes need to be made by site owners to work smoothly with IE7.  We have produced detailed documentation, tools and other resources to assist site, extension and application owners in their testing and development efforts to ensure they are compatible with IE7.  We have also proactively worked with hundreds of companies to resolve issues that were reported through our beta testing to ensure those issues were resolved before IE7 is released.

These efforts have been ongoing since last year and have been extremely successful but we can’t ensure 100% compatibility without your help. We need you to test and ensure your sites, extensions, and applications are ready for IE7. We strongly encourage you to do the following ASAP:

Download, install and test your products with IE7 RC 1 –This is the fastest and best way to test for compatibility issues.

Download the IE7 Readiness Toolkit - This toolkit pulls together a number of important resources to help you prepare for IE7:

Developer and IT Pro readiness check lists,
Detailed documentation on important changes in IE7,
Testing and debugging guidance,
Tools for testing, debugging and investigating issues,
And more…

Download and use the Application Compatibility Toolkit – Helps test browser-based applications to ensure they work with IE7.

Visit the Microsoft Internet Explorer Developer Center – You will find an array of important information for developers.

Use the Information Index for Internet Explorer7 – Think of this as a table of contents linking you to documentation, blog posts, whitepapers and other information on IE7.

Read the IE Team Blog – Use the search feature on the right to find previous posts on almost any topic you can think of with regard to IE7.

What if my organization is not going to be ready for IE7 in time?

Organizations that are using Automatic Updates in their environments can block the AU deployment of IE7.  For more details check out the “Options for Blocking Automatic Delivery” section of our Automatic Delivery of Internet Explorer 7 article.

We hope that you are as ready and excited about IE7 as we are. If you have feedback or encounter any issues, check out the IE7 Support page for FAQs, Release Notes, and feedback options.

Thank you,

Scott Graff
Program Manager – IE7 Compatibility
Microsoft Corporation

Comments (333)

  1. Jeff Luckett says:

    My company is having problems with IE7 and Authorware 6.5. We have online courseware that opens in a seperate window in IE6 but doesn’t do anything in IE7.

    Where would I inquire and pass on our tech info to get help?

    thanks and good work!


  2. Ron says:

    I’m getting nervous, my work life is about to get a lot more complicated.

  3. Fubar says:

    Our organization will install it 6 months after it’s released.

  4. Klimax says:

    Unfortunately I cannot install IE7 on company computers,because Komercni banka ( and still did not updated their on-lineaccess to account.

  5. Michael says:

    how can i backup my IE7 RSS list?

    u know,i wanna ghost my OS back,and my ghosted OS only has IE6sp1 on it.

  6. Ben Hollis says:

    What is the reccommendation for people who will need a copy of IE6 around to test website compatibility, and will also need IE7?

  7. a says:

    They suggest using Virtual PC (Honestly).

  8. Al Billings says:

    IE6 and IE7 are not going to work reliably side by side. I think the best suggestion is Virtual PC or two computers. This is the same answer as has been given every time this has been asked for the last year… I seriously doubt you will get a different one.

  9. Wilfred Khor says:

    Thanks, but will remain using IE6 on the company computers until my customers update their sites to compatible with IE7.

  10. JD on EP says:

    IE7 soon: Microsoft advises compatibility testing of existing websites now. There are links here for changelists, checklists, and debugging tips. There’s an "Application Compatibility Toolkit" for web applications in WWW browsers… I’m not certain how

  11. coreyb says:

    My only question and concern is will IE7 actually follow CSS3 or even CSS2.1

    If Explorer will follow STANDARDS then we would not have to "test" so much.

  12. Neil says:

    This seems horribly backwards to me. "We need you to test and ensure your sites, extensions, and applications are ready for IE7."

    I may have an idealist view of the web, but shouldn’t a new browser accomodate existing sites, rather than sites accomodating a new browser? I understand that there’s a give and take regarding new browser features allowing people to design their sites in ways that were previously impossible but don’t we have standards and whatnot so that when a new browser is released existing sites just work?

    I know all of this is something that has been said before. What really puzzles me is that a company (any company) can be this close to launching a browser without discarding the idea that the web should ready itself to accomodate their browser. It seems very concieted, sloppy and contrary to the principles that make this whole system work.

    Regardless of all that, six months from now the browser will be launched, sites will be updated and this whole discussion will be forgotten with few lessons learned.

  13. Arieta says:

    Hopefully the final version will be able to actually display pictures instead of timing out after 2 seconds into loading with a red x.

    Also, you can’t click on links from Outlook Express emails. It just pops up an empty browser window.

    I’m also getting a lot of IE7 crashes lately with RC1.

  14. DanAlavan says:

    CAREFUL!  If you don’t have genuine Windows, IE7 will either not install or worse.

  15. zach says:

    Al Billings, I’m glad to see you back posting here in the IEBLOG.

  16. derek says:

    There is no way that IE7 is ready did you get css to work if not return to sender no digg!

  17. BOB says:

    This seems horribly backwards to me. "We need you to test and ensure your sites, extensions, and applications are ready for IE7."

    Correct there is no way you make a page for the browser stop the madness for Microsoft.

    it should say:

    Is IE7 ready for the internet?

  18. To the people who are worried about testing on IE6 and IE7, I have been using the unofficial IE6 standalone alogside IE7 with few problems. It doesn’t really work as a browser, but it’s fine in 99% of cases for checking layout. Don’t shell out of VirtualPC – get the standalone from, and keep IE6 installed on a old PC so you can do a final check with the real thing.

    In my experience the IE6 standalone has two drawbacks – transparency doesn’t work properly and random dialog boxes sometimes appear when you load a page. CSS layout is fine.

  19. Dominic says:

    "Oh, no! We thought you were kidding. For real? There’s actually going to be a new browser and it could break my website?"

    That’s the reaction I’ve been getting. Lots of folks are nowhere near being ready. And often the problems relate to Microsoft stuff.

    The latest I’ve noticed is how PowerPoint presentations saved as HTML don’t work at all.  Lots of companies do this.

    Hope you’ve got your PR key messages all figured out.

  20. Benjamin Hawkes-Lewis says:

    Ben Hollis,

    As others have said, Microsoft has previously recommended a Virtual PC (or a second machine) to run IE6 side-by-side with IE7. VMWare is obviously another option. If you can’t afford yet another copy of Windows just for IE6, then you might like to read Position is Everything’s guide to running multiple copies of IE on the same Windows installation:

    I don’t know what the IE team’s view of that technique is, however.


    "I may have an idealist view of the web, but shouldn’t a new browser accomodate existing sites, rather than sites accomodating a new browser? I understand that there’s a give and

    take regarding new browser features allowing people to design their sites in ways that were

    previously impossible but don’t we have standards and whatnot so that when a new browser is released existing sites just work?"

    I’m afraid not. That would of course be true if browser developers and web designers had followed standards earlier, rather than building a castle in the sky with proprietory features, quirks, and hacks. It is in large measure its greater respect for web standards that leads IE7 into incompatibility with many existing sites. Sites designed simply according to the standards, ignoring Internet Explorer’s support or lack of support, should work better in IE7 than in IE6.

    This process will be an uphill struggle, of course. This page you’re reading now is "invalid XHTML" (a phrase that deceives in implying that invalid XHTML is still XHTML, rather than tag soup) in no less than 77 different ways:

    If you want to know how to code sites that will work in most user agents for most users:

    1. Read and follow the HTML 4.01 specification, the CSS1 specification, and the DOM Level 1 and 2 specifications at the W3C site. Do NOT trust the highly inaccurate renditions of these specifications at MSDN and W3Schools (and if you find errors, report them to the maintainers of those sites). Validate your HTML and CSS with the W3C validators.

    2. Separate structural/semantic markup (e.g. HTML elements and microformat classes) from presentation (external CSS files imported with LINK) and behavior (external JS files imported with SCRIPT in HEAD). Ensure that these can work independently of one another.

    3. Make sure ALL images have alternative text specified with an ALT attribute. If the image is purely decorative, use ALT="". If you have lengthy navigation, provide a "Skip navigation" link so people with disabilities can jump directly to your all-important content. Never rely on color alone (e.g. colorblind users often can’t tell red links from black text). For more accessibility guidance, see the W3C’s Web Content Accessibility Guidelines (WCAG).

    These strictures may be difficult to implement with "web applications", as opposed to ordinary information- or commerce-oriented websites. However, standards and accessibility techniques for web applications are in active development by browser makers, cutting edge web designers, and spec writers. So the more use you can make of existing standards in web applications now, the easier and cheaper it will be to adapt them to the standards of the future.

    If you need help on how to make standards-based sites, the #css, #html, #web, and #xhtml channels on Freenode IRC are full of people keen to offer advice.

    while it may be hard at times, anything that moves us towards a more standards-based web should make web development more efficient and effective in the long run. Be idealistic! Be brave!

  21. Cyril says:

    After the release, will you continue to develop IE7 ?

  22. David William Wrixon says:

    Instead of worrying about the trivialities that are going to affect some American sites and trust me they are far and few between, having used IE 7 all day every day for months now, you should be more concerned of the ongoing damage that is being caused to Developing World economies due to lack of support for URLs that actually mean anything. It is introspective naval gazing like this that make it wholly inappropriate for the US to continue in its role of Internet Governance.

  23. Francis says:

    I am waiting for this final release.

    However, at least the two following incompatibilities prevented me from upgrading from Bet2 to Beta3 or RC1:

    – Norton Internet Security

    – HP Director

    Do you know if they will be solved at the time final release is available

  24. goose says:

    Microsoft is the best!!! IE7 will make the web safer from all the spyware I got in Firefox and Opera and Safari. Everyone knows Microsoft makes the standards, not standards bodies like W3C. Make sure your site works with it or face financial and ego RUIN!!!!!

    Microsoft can buy you and your governments, so listen to them and have some respect for the best browser on EARTH!!!! A lot of work went into it! Nothing comes close! Pay your respects. RC1 is fine. Amazing. Great. Anti-phishing ahoy.

  25. Dao says:

    Just discovered a bug, and I’m tired of

    You’re finally using the -ms- prefix, fine! But the scripting representation of this property should be MsInterpolationMode (-ms-interpolation-mode), not msInterpolationMode (ms-interpolation-mode).

  26. says:

    Microsoft anuncia el lanzamiento del Internet Explorer 7 para fines de mes. En su sitio han agregado una lista de consejos para que tus sitios, extensiones y aplicaciones sean compatibles con el IE7. Como dicen en el IE 7 blog , Are you ready?

  27. ideami says:

    i hope they will have added tabbing which is something i miss very much in explorer

  28. Keith says:

    I’ll be waiting for IE 7 to be publicly released. I’ve been using it since IE 7 Beta 1, and see the improvement at every development stage. No reason why I should give this a miss.

  29. Engelmajer says:

    I’m waiting for IE7, to give it a try..

    i don’t user IE6 at all, because it’s much easier and better to user Firefox or similar browsers..

    I don’t agree when you ask us to check our sites, to see if they are compatible with IE7. if they are not compatible that’s IE6’s fault, every sites have something to fix "this or that" to work on IE6.. so if they will make them look like a mess on IE7 that’s not our fault.

  30. Internet Explorer 7 will be released this month, acording to Microsoft, and will be installed via automatic updates. Story includes links for webmasters compatibility tools and checklists.

  31. Skidmark says:

    I have a couple of websites which have .swf flash files in them for navigation. With IE 6, you have to click on the part of the page which has the file or hit the space bar or enter to activate the file and its contents. I tryed downloading and installing IE 7 and it does the same thing. Mozilla Firefox does not require this. I have put notes on my pages advising my friends and customers that is they don’t want to contend with this, to go download Firefox. I personally think it works better anyhow. It also appears that with IE 7, Microsoft is trying to get a more Firefox look (tab browsing)

  32. Dao says:

    > I have a couple of websites which have .swf flash files in them for navigation.

    Sounds like an annoyance to the user, rather than a feature.

    > I don’t understand… What the hell am I supposed to do when IE7 is released? My sites are W3C compliant. Why should I make sure, my sites work with IE7?

    If your site is W3C compliant, chances are good that it works better with IE7 than with IE6.

  33. Neil says:


    "That would of course be true if browser developers and web designers had followed standards earlier, rather than building a castle in the sky with proprietory features, quirks, and hacks. It is in large measure its greater respect for web standards that leads IE7 into incompatibility with many existing sites."

    What you’re saying has a grain of truth, but I don’t think it applies to the big picture. I’ve been around long enough to remember how IBM Web Explorer used the ‘frame’ tag to change the loading animation in the page. There’s one of your proprietary features. The other side of the coin is how IE3 reacted to that use of the ‘frame’ tag. Errors in the text of your site. Not error dialogs. Not quietly ignoring it. That old version actually changed the content of your page when it came across markup it didn’t like.

    Sure it’s an old and obscure example, but that’s the kind of thing that designers have been forced to work around since the earliest days of the web. Now IE7 is asking us to do the same, but this time in the name of ‘compatibility’.

    If all this is really in the name of compatibility and standards compliance, I will happily eat my words.

  34. Bambooocha says:

    Where is the Polish language? 40 ml people countery!

  35. Bloopy says:

    IE7 Is Coming This Month…Are your parents ready?

  36. PJ says:

    IE7 broke my site that works in IE6 and Firefox.  

    Simply use the IE "comment" tag to ignore IE-specific problems.  

  37. J. Rivera says:

    I cannot believe we will be forced to download IE7 through automatic updates. IE7 should be provided by default (as is already) on future MS operating system’s while given "savy" users on older operating system’s the choice of downloading and installing. I wonder if IE6 will continue to receive updates after IE7 is released?

  38. Eduardo valencia says:

    Good work,keep updating IE!!,make it the best (still not)

  39. Mike Dimmick says:

    Ironically, the sites with the fewest problems are probably those that don’t declare a DOCTYPE, since Quirks Mode rendering is largely untouched. The sites that have the most problems are those which declare a DOCTYPE (invoking ‘Standards’ Mode on both IE6 and IE7) but which then use ‘Hacks’ to work around bugs in IE6’s rendering. Many of these hacks no longer work on IE7. In some other cases, a different stylesheet has been supplied to IE6 which works around bugs in IE6’s rendering; if the browser detection still detects IE7 as IE6, the workarounds then cause problems for IE7’s corrected rendering.

    The problem is that many sites were developed within the last five years and work around problems in IE6, but are no longer maintained. These sites may not work well in IE7.

  40. Mike Dimmick says:

    Michael: to back up your RSS feeds, click the ‘Add to Favorites’ button (yellow star with green +) and choose Import and Export from the menu. Click Next, then select Export Feeds and Next, select the location to export the feeds to, click Next, then Finish.

    It should be possible to import the resulting OPML file into any RSS reader – it’s a standard format.

  41. Mike Dimmick says:

    Skidmark: this behaviour is a result of the patent decision by a US court, known as ‘the Eolas patent’. Microsoft would have to pay a huge royalty to Eolas if they were to support automatic activation of ActiveX controls or other plugin code. Mozilla Foundation and Opera have not yet been sued. Microsoft are appealing the case.

    In my view, the court is wrong, and I hope this will eventually be killed off.

    To work around the issue, see

  42. Munitions says:

    Ready for what?

    ‘Nuff said.

  43. TechBlog says:

    Scott Graff writes at the IE7 Blog that the final release of Internet Explorer 7 is almost upon us — as in, this month. He also reveals a little more about how its distribution through Windows Update will be handled:…

  44. JD on EP says:

    JS in November: Mozilla Firefox 2 is now in Release Candidate 2 stage, joining Microsoft Internet Explorer 7 in final public compatibility testing. I can’t remember the last time we’ve seen two major browsers arrive so closely together. I’m guessing new

  45. Mike Weller says:

    Fix the CSS support properly.

    The funny thing is, you know this is what we developers want… we want BETTER CSS support, but no you’re deciding to release it anyway.

    Oh well.

  46. George says:

    I am excited about the final IE7 release this month… But as a microsoft fan i am concerned with the decision to install IE7 thro automatic updates in just few weeks after the final release.

    I would like MS to wait atleast 3-6 months after the final release for automatic mass distribution. You may never know what kind of issues will come up with IE7 in a real user environment and this 3-6 months time delay will help to stabilize the software with necessary updates.

  47. According to Microsoft’s IEBlog, IE7 is coming this month — Are you Ready? Most of the expected compatibility issues are in CSS filter hacks that will no longer work in IE7. However, in working with the IE 7 Release Candidate…

  48. musti says:

    W3C is ready, for a long long time. The question is, is IE7 ready?

    Yes, didn’t think so either.

  49. Danny says:

    Hey Team,

    although the changes made in IE7 are a step in the right direction (andit’s great you made that step), the way you’re actually going is the wrong.

    I know it’s been said many times. IE need a rewrite ot it’s rendering engine.

    – Please listen -, since the end of the Browser War, every great rendering engine had a rewrite from scratch. And guess what? "IE optimized" sites still work in them. They’ve got a Quirks Mode and all that chit chat as well. The only sites that don’t work in those browsers are pages written in the worst possible style.

    Working on the Trindent Engine seems like an act of desperation. This engine IS buggy. We all know. Sure, you’re fixing some of them but you’re loosing sight of the real problem: hasLayout and all that things stand in the way of joining the right way.

    For all User’s and Webdesigner’s sake. Going on with the Trident engine is the way Netscape 4 went.

    Rewriting the Engine WILL take a lot of time, no one can hide that fact. But from another point of view: that time can be uses for your customers (especially writers of WebApps) are to be informed of good webdesigning style.

    As said, there are only few sites which really don’t work in alternative browsers (some even do but are just stating otherwise). Taking this into account, your argument about breaking some pages are not that important as you might want to believe.

    I’m sorry for writing that much. I hope I wrote something objective (and that someone is reading this ^.-).

    And I truly hope you will come to mind and leave the way before History repeats itself.

    By the Way: I salute to Mister Wilson.

  50. What’s interesting here is the team will be forcing IE7 installs out through normal Automatic Updates

  51. I’m now seeing in RC1 security alerts for plug-in detection scripts for the QuickTime ActiveX conrtrol. Such scripts are commonly used for detection/degradation strategies and by stats packages for reporting on the various plug-ins/controls available in an audience.

    Is there something Apple needs to do in order to make the QT Control pass the security inspection?

  52. Kalle says:

    RC 1 is not running on my windows xp machine. When I open a tab the explorer shuts down!!!

  53. figgy says:

    "Microsoft is the best!!! IE7 will make the web safer from all the spyware I got in Firefox and Opera and Safari. Everyone knows Microsoft makes the standards, not standards bodies like W3C. Make sure your site works with it or face financial and ego RUIN!!!!!

    Microsoft can buy you and your governments, so listen to them and have some respect for the best browser on EARTH!!!! A lot of work went into it! Nothing comes close! Pay your respects. RC1 is fine. Amazing. Great. Anti-phishing ahoy.


    You obviously have no clue what you are talking about.  You do not understand the CSS box model nor do you seem to care.

    Further, everytime I post a comment on this blog that doesn’t cheer on IE, my comments are removed.  Nice work MS.  Thanks for the freedom and speech.

    Bottom line is, IE 7 in not compliant either and will make a lot of problems for a lot of people.  Even though MS must realize this, they are forcing it upon all of the world through an automatic system update.  Nice, thanks, we really appreciate that MS (not).

  54. Ben Hollis says:

    So I’ll need to create a Virtual PC install of WinXP (which requires a separate XP license?) and then prevent that from getting the IE7 update (be careful now) and then I can test in IE6 and IE7? Hm.

  55. PatriotB says:

    @J. Rivera: "I cannot believe we will be forced to download IE7 through automatic updates."

    Automatic Updates alerts users to the availability of IE7.  Users can then choose 1) install it now, 2) don’t install it and don’t ask me again, 3) ask me later

    "IE7 should be provided by default (as is already) on future MS operating system’s while given "savy" users on older operating system’s the choice of downloading and installing."

    The goal is to spread IE7 to less savvy users as well.  There are a lot of security and rendering improvements, thus MS, and the general web dev community, wants to see as quick adoption of IE7 as possible.

    "I wonder if IE6 will continue to receive updates after IE7 is released?"

    Yes, MS has stated that IE6 will continue to be supported (i.e. get security updates) as part of XP as long as XP itself is supported.  And IE6 SP1 on Windows 2000 will be supported as long as 2000 is supported.

  56. Michael says:

    There has been much said about CSS support – or lack of, here. I have been trying to address a problem related to CSS that I can’t seem to find an answer to and it seems no one wants to acknowledge. Visual Studio’s (both 2003 and 2005) style builder has been broken by the installation of IE7 since beta 2. There was a fix for the original variation of the problem by adding devenv.exe to the feature control section of IE’s registry hive in HKLM. Beta 3 and RC1 reintroduced the bug and the reg entry does not help.

    The style builder comes up with none of the fields populated when trying to edit an existing stylen – both from a CSS file and the property sheet in the visual designer. From what little I’ve been able to deduce it is caused by the preview pane which requires IE to render, getting an access denied error that we can’t see. I’ve tried to report this on both the VS and IE forums and no one has bothered to answer the posts. I know it’s not an issolated problem with my dev PC as it is repeatable on clean builds as well as on Vista. Uninstalling IE7 restores the style builder functionality. I also tried to install the beta SP1 for VS2005 and that not only didn’t fix the problem it introduced a plethera of new ones.

    I’ll be watching this blog to see if anyone answers my issue. I really like IE7 and do not want to return to IE6. This is the only issue I’m having with it that I can’t work around or live with. Please help!

  57. Michael says:

    Just a comment here that it is really a bad idea to not make IE7 work on ALL the versions of Windows that currently support IE6. I can understand why the IE team wants to get IE7 out ASAP as it will no doubt help with the overall issues relating to IE but there is still a very large base of users out there that can’t/won’t update to WinXP/2K3/Vista. I for one have several Win2K servers that I need to keep and can’t be updated to Win2K3. I would really like to have IE7 on them instead of IE6. I guess I’m just SOL as this seems to be a top down directive and not a (valid) technical one. Too bad for me.

  58. MrDale says:

    I’m also getting a lot of IE7 crashes lately with RC1…

    Me Too. It’s lie the browser has been working for the last 5 minutes to just dissapear on me. Happens at least once a day and I always send Error Reports.

    I also hope IE 7 Final fixes the issues it has with Flash 9, since IE 7 shutdowns at least once a day for me when I have a site up that uses flash due to a Flash 9 error. Never had this problem until Flash 9 came out, but there’s no issues whatsoever in Firefox.

    Other than that, it looks good. The speed in opening pages and loading tabs from favorites is slower than Firefox, but Firefox’s 2 right now, is pretty crappy.

  59. mkavici says:

    no we are not (web developers and designers), and we won’t be unless IE7 gets ready for W3C standards!

  60. Dao says:



    > You’re finally using the -ms- prefix, fine! But the scripting representation of this property should be

    > MsInterpolationMode (-ms-interpolation-mode), not msInterpolationMode (ms-interpolation-mode).

    Furthermore, your newly introduced keywords ‘bicubic’ and ‘nearest-neighbor’ should have the -ms- prefix, too.

  61. TheViewMaster says:

    You Are NOT Releasing IE7 With This Reduced "FULL SCREEN" Functionality, Are You???


  62. CSS Guy says:

    Does that mean IE will finally render standard-conform pages by the rules? I mean, really? Not just marketing blabla, like the lsat 5 or so versions?

    In any case, I rather wait for Service Pack 1 before I download. Bad experiences, you know.. .-)


  63. . says:

    W3C and CSS is not supported because they are obsolete garbage.

  64. Developer says:

    Once again, a reminder that developers are forced to fork over unnecessary money for a whole new computer or a useless piece of software just so we can do PROPER testing like running IEs side by side.

    By the way, the CSS support in IE7 is still causing more headaches than its worth and the interface is just plain confusing. Fix it, then release it.

  65. I am a student heading towards Web Development. Because as a student I cannot afford a second computer for testing on different versions of IE, I would like to know if there is any free, trustworthy, and simple software available to have both IE6 and IE7 installed on XP without them interfering with each other. I have a feeling that most developers would like this, and some of the more skeptical regular users would as well so that they can try it out without affecting their current settings.

  66. Jeff Allen says:

    When is IE7 coming this month?  I’m ready as I’ve been testing IE7 RC1 on several systems.

  67. @ IE Team – A lot of Microsoft’s programs that do not open in the default browser but in IE (wonder why? ;-)) do not open in a new tab but a new window. Has that been fixed? Has the opens in IE and not default browser issue been fixed or is this handed down as a final decision?

    @ IE Team – I like being able to use the IE6 GUI with 7’s rendering engine. Is there any chance we could see IE7’s feature’s get added to the IE6 GUI? I don’t imagine this would be too difficult?

    @ IE Team – Any chance we could get :focus enabled? Only Gecko supports it properly (and Opera has exceptionally buggy support for it).

    @ IE Team – Releasing IE7 through Windows Update is probably one of the best moves though honestly there are some questionable reasons why some people in the company have forced you to do this (though I’m sure your team’s reasons are legit).

    @ Neil "I may have an idealist view of the web, but shouldn’t a new browser accommodate existing sites, rather than sites accommodating a new browser?"

    That would be true if websites were correctly written. IE handles incorrectly written websites very well, it’s people who code correctly like me that Microsoft needs to be working with and they have.

    @ Chris Ovenden – That "IE 6 Standalone" does not work at all. Evolt needs to take that "standalone" down.

    @ Francis – Uninstall the useless Norton weedware from your computer.

    @ Skidmark – Stop using flash for your menus unless you’ve disabled Flash and have thoroughly tested your object’s alternative content.

    @ soc – Just serve your pages as application/xhtml+xml if you want to block IE users access. IE does not support XHTML though it has supported XML since 5.0.

    @ Mike Dimmick – The reason non-doctype sites work well in IE is because of the huge non-standards support that is in IE. My site meets all of the highest levels of standards and required very minimal IECCSS to get it to work correctly for IE7. It dropped from code red to code orange (lack of application/xhtml+xml support) though would otherwise meet code yellow.

    @ figgy – Posts are pre-moderated and I think whoever is moderating it is allowing much of the not-on-topic anti-Microsoft sentiment through to be given much credit. Save your posts and email them to me if they don’t get approved and I’ll be glad to let you know why they didn’t get posted!

    @ Not IE6 standaloners – At least IE7 can be uninstalled. If you don’t like not having standalones then test your sites out correctly by using IE6 with IECCSS and then install IE7 and use a different IECCSS.

    Honestly if people code their sites correctly a new version of any browser will not effect a site negatively and adding support for continued bugs for those newer browsers will diminish over time and should not effect older versions of those browsers.

  68. Jack Yan says:

    I have found an incompatibility, and it is not dissimilar to the one that I discovered on Netscape 6 and its successors (including Firefox), though the relevant posts at this blog are closed. Hope you guys can help: I have Adobe Type Manager installed and generally use PS1 fonts. However, my TrueType fonts do not display properly: whenever there is a ligature (HTML fi and fl for fi and fl), IE7 changes fonts on me, just for those characters. This never used to happen—it has been something IE has always managed to do since version 5, properly (and something that Netscape could do up to version 4.7). My own blog could be a place where you can see this happening, and I can send screen shots if necessary.

  69. Ray says:

    Now, this isn’t a IE thing, it’s about the site in general.

    Alot of the freakin’ site has stopped working, the ‘contact us’ link down the bottom is broken, the ‘’ site is broken, all i get is a ‘Runtime error’ page, and when i tried to email ‘’ i got a bounceback saying the mail server is broken.

    Can this please be looked into ?

  70. Alex says:

    I’ve got aquestion about IE7’s handling of the case of Suckerfish Dropdowns. I’ve simplified the code to exclude the IE6-specific css rules applied by the suckerfish javescript, so they look shorter than the rules you’ll find.

    Why does this work:

    .nav, .nav ul {padding: 0; margin: 0; }

    .nav a {display: block; width: 10em; }

    .nav li {float: left; width: 10em; }

    .nav li ul {position: absolute; left: -999em; }

    .nav li:hover ul {left: auto; width: 10em; }

    While this does not:

    .nav, .nav ul {padding: 0; margin: 0; }

    .nav a {display: block; width: 10em; }

    .nav li {float: left; width: 10em; }

    .nav li ul {position: absolute; width: 10em; left: -999em; }

    .nav li:hover ul {left: auto; }

    As a pseudo-element, shouldn’t the li width trickle down to the li:hover rule?

  71. PatriotB says:

    @John A. Bilicki III: "A lot of Microsoft’s programs that do not open in the default browser but in IE (wonder why? ;-)) do not open in a new tab but a new window. Has that been fixed? Has the opens in IE and not default browser issue been fixed or is this handed down as a final decision?"

    Properly coded programs will always use the default browser (e.g. those that call ShellExecute("http://…")).  If clicking a link in some MS program ignores your default browser, then that program is at fault and needs to be changed; there’s nothing IE can do about that.

    Ignoring the default browser could happen in one of several ways.

    1) The app specifically executes "C:Program FilesInternet Exploreriexplore.exe" passing it the web address.  I think that this will always create a new window, and i think it always should; if I as a user were to start > run > iexplore, I would expect a fresh IE window.

    2) The app uses DDE to ask an existing IE process to open a given URL.  I believe that this will always obey the "new tab" setting.  Usually, though, a program won’t use DDE; usually just the shell itself uses it (via the aforementioned ShellExecute).

    3) The app uses COM to instantiate an InternetExplorer COM object.  By definition, this object is a new top-level IE window.

    Thus in cases 1 and 3, there is nothing that can be done about the new window vs. new tab, because the calling program is requesting a new window.  The calling programs will have to be changed.

  72. *prepared to be flamed*

    I for one am very eager for IE7 to be released. The team has made significant (though not total) improvement on its rendering engine, and it will only get better as time progresses. They’ve caught up many years this release, next release they will catch up all the way. Maybe even by SP1.

    In saying ‘Prepare your site for IE7’, I believe they are referring to sites that browser-sniff for IE and render with hacks. Most of those hacks can now be safely removed as they will now render incorrectly with IE7’s improved CSS support.

  73. EricLaw [MSFT] says:

    @Kalle: Kalle, crashing on tab creation is a symptom of a buggy older version of Google Desktop search.  Upgrade to the latest version to avoid this problem.

    @figgy: He’s being sarcastic.  

    @Michael: There are many technical reasons that IE7 is not available on Win2k.  IE7 relies on quite a few APIs that are only available in XP and above.

    @John A. Bilicki III:

    1> I’m not aware of any current MS applications that don’t use the system default browser for hyperlinks.  With regard to the new tab: If you’ve configured IE this way, it should reuse existing windows for virtually all applications.  The one common exception is Outlook Express, which doesn’t work correctly because they CoCreate IE (if it’s the default) rather than launching via ShellExec.  Windows Live Mail does not suffer from this problem.

    2> No, there’s no way to plug the IE7 rendering engine into the IE6 UI.  This would actually be quite an undertaking even if it had been a design goal.

    3> No one "forced us" to offer IE7 via AutoUpdate.  IE7 contains significantly improved security over IE6, and hence IE7 is entirely suitable for AutoUpdate.  As noted, it’s entirely up to the user to decide if they want to install it.

  74. Luke Angel says:

    I want to know why we have to wait till IE8 to get a download manager? the Mac version has had this for years and is now discontinued. We are still very behind in the IE Field.

    Time to play catchup guys!!!

  75. haoyuming says:

    you will find a lot of chinese domain names at

  76. After a while, Microsoft IE is back in the spotlight. According to the Microsoft Internet Explorer Blog, the final versio…

  77. rickz says:

    My company it’s ready for IE7.

    Keep up the good work team.

  78. Mike says:

    IE and all versions of it sucks, yeah I’m ready…I’m ready to decline the update when it prompts me for it.  And I’ll just stick with my RELIABLE Firefox thank you very much.

  79. my name says:

    can’t install it. even when i do all the tipps and hints from m$. poor. very poor.

  80. Joachim Jonkers says:

    I’ve enjoyed the beta very much, thanks for all the good work. And I’ve read that Microsoft cooperates with Mozilla (a team of Firefox-coders was invited to Redmond).

  81. EricLaw [MSFT] says:

    @Luke Angel: There are lots of good add-ons for IE download managers.  See for some suggestions for this and other addons.

  82. IE7 vil komme i løbet af denne måned. Er du klar til den kommer? Har du testet dine web sider, plug-ins

  83. Benjamin Hawkes-Lewis says:

    [This was part of a longer comment that got eaten by the moderation monster for some reason I can’t work out. Maybe it was too long? Too many links? Used curly quotes? Other comments on this thread have been much more critical of Microsoft where as I repeatedly defended them on certain crucial points, so I don’t think it was censored.]

    David William Wrixon:

    I haven’t really followed this issue, but…

    (1) I thought IE7 *did* support internationalized URIs:

    Is this support broken in some fundamental way?

    (2) You’re of course right that web development has been radically distorted by its English-speaking focus. But presumably international web users have for some time been able to make use of browsers like Safari, Netscape, and Firefox that (if I understand correctly) already support internationalized URIs? Roughly speaking, are not Apple, AOL, and Mozilla Foundation as American (or not) as Microsoft? In any case, note that IE6 was introduced in 2001, before IDNA became a standard (2003):

    (3) The "trivialities" affect international web development too (indeed perhaps more so, as developing countries are poorer and can less afford to deal with them).

  84. Benjamin Hawkes-Lewis says:

    [Hurrah! Let’s try another one.]


    I have used Norton Internet Security 2005 with IE7 Release Candidate on Windows XP Professional with no apparent problems. Your mileage may vary.

  85. You just should implement the w3 standards instead of saying that we have to adapt our sites to your browser.

    Thanks God there is no IE on GNU/Linux

  86. Blog::David says:

    Je viens de lire sur " The Microsoft Internet Explorer Weblog " que IE 7 pourrait être proposé ce mois

  87. Sereby says:

    i have a little bug with the newest IE7. is this fixed in Final?

    i have some folders in my favorites and if i have the IE opened a while i cannot reopen some of the folders! i have to restart the ie that it work again 🙁

    and i locked the favorites but its resizing ever time! its growing and growing! i have to resize it every time..

  88. Benjamin Hawkes-Lewis says:

    [Okay, now I’m leaning towards the theory that their moderation monster assumes comments with lots of links are spam and gobbles them. I’d like to back up more of what I say here, but oh well.]


    "my sites are always w3c-compliant. i don’t give a [expletive deleted] about your fancy ie7. … i’m blocking access to my private sites for people which use ie. if they don’t care how my page really looks, they can go elsewhere."

    If the service your site provides *requires* (or even benefits from) a standard feature unsupported by IE, that is one thing. But going out of your way to block access to IE users punitively or automatically, including (inevitably) those visually disabled users who have to use IE because it is the only browser supported by their screen reader of choice, is *not* in the spirit of W3C compliance. WCAG especially asks you to take into account that your visitors "may have an early version of a browser, a different browser entirely, a voice browser, or a different operating system".

    John A. Bilicki III suggests: "Just serve your pages as application/xhtml+xml if you want to block IE users access. IE does not support XHTML though it has supported XML since 5.0." If the aim is to target IE users then this is a bad idea, since it will also lock out Lynx and produce buggy renderings in ELinks. Conversely, it won’t block IE users with MathPlayer 2.0 installed.

    If you really want to encourage people to use browsers with a given feature set, you could provide fallback content which provides the *same* service to browsers that do not support those features but which advertizes that a better experience of that service is only a download away.

    Sadly, there is no fully-featured, free, general purpose screen reader that does not require IE. Perhaps rather than devising new ways to punish IE users, we should be working on that?

  89. John Christman says:

    My company uses Microsoft Groove 3.1.  IE7 does not work Groove, unless you use the 2007 Beta.  Will either IE7 or Groove 3.1 be changed to work together?  Or are there changes you can make to the configuration to make them work together?

  90. Alex says:

    Why using IE7 ? When you have standard compliant browser more stable, more secure, more extensible and free software (free as in freedom)… The better question is ready for Firefox 2.0 😉

  91. Michael W says:

    Well the only webhosting websites are those that are hosted by world now. If you go to a website using this host some of the link’s will not work. But other then that Ie7 will be a good program when all the bugs are fixed .


    Ps. I’m using IE7 rc1 Now and it work very will . Besides the small bugs .  

  92. Bob says:

    Very nice, RC3 is working perfectly, I’m looking forward very much to learning what else is new.

    Oh, and off-topic: the CSS specification is bloated, inconsistent, illogical (the width of a box should specify the actual width of a box. When I set the width of a box, I shouldn’t have to calculate with margins to determine the -actual- width. Sorry, but MS’s interpretation of the box model makes more sense.), and fails at its goal of actually separating layout from content in a normal fashion. Also, anybody can say that he has created a standard. What matters is which of these standards -becomes- the de facto standard in the world.

    Looking forward to it, guys. Any chance of a post about the changes since RC3?

  93. . says:

    Ok, everyone should just shut up, and wait. If then it does not work for you when released just downgrade. Simple as that.

  94. Martin T says:

    Can you actuelly downgrade, to ie6 if you get the ie7 as part of the automatic security update? I mean none of the other security updates have an uninstall option, so have there been made a special case for ie7? (I had to disable automatic update because I don’t want ie7(Need to test websites on ie6), but if I can just install it again that would not be a problem))


  95. Yeah says:

    Thanks for giving us money to make things work in IE 6 as intended and give us money again to make things work as they used to work in IE 7 but well, not really  ;p

    We ll just add new TagSoup and Quirks cause you cant do a good browser but just TagSoup Parsers.

  96. sibyl says:

    I love IE 7 RC 1 but I do wish they would consider (and Im doubting it highly) making the menu more configurable:

    i.e.  (no pun in tended)  

    being able to not show the Google toolbar

    being able to move things around on the menu

    as it is now things are all over the place and cannot be moved as they can with IE 6 or any other browser out here.

    I repeat.. I love it.  It has been stable for me,  runs very fast.  Its just this new menu that drives me NUTS

  97. JasonR says:

    Is IE 7.0 compatible with OmniPass software? This software is use for APC Biopod Biometric Password Manager(Fingerprint reader).

  98. Steve says:

    I had a machine with XP Home with IE7, when I upgraded to XP Pro I had tons of issues that all had to do with authenticating my XP key after XP Pro was installed.

  99. Michael says:

    I’M a big IE-fan – and have been using it for the last 12 years. It’s a bit hard these days to be a fan with your very slow formatting-engine.

    I have been testing your beta for a long time – it’s very very slow to format the page.

    Hope this will be resolved.

    Best regards

    Michael Christensen

  100. Jim says:

    I think IE7 is fantastic. Microsoft has done a good job, even if it has been a long time coming. Its fixed and improved upon many things that were wrong with IE6. My Intranet works just the way it did in IE6 with the exception that it loads a lot quicker. I look foward to the final release.

    Well done Microsoft!

  101. crohno 2 says:

    oh i forget, IE makes webpages goes wrong because doesn’t accept W3C, so if u want to see webpages correctly use firefox or opera(safaria, camino or whatever browser u want but not IE please!!!)

  102. Mr X says:


    the question: Is Microsoft ready?

    Are all these bugs fixed?

    (click through Seite 1-3 and switch between another Browser (eg Firefox) and Internet Explorer 7)

    I think the examples say more than any written explanation.

    MfG Mr X

  103. PatriotB says:

    @Martin T: "Can you actuelly downgrade, to ie6 if you get the ie7 as part of the automatic security update? I mean none of the other security updates have an uninstall option, so have there been made a special case for ie7?"

    If you install IE7, you can always uninstall it and go back to IE6.

    And actually, the majority of security updates I’ve seen are uninstallable.  In fact, on my machine, every security update under "Windows" is uninstallable; only some "Office" security updates are uninstallable.

    You may not be seeing any of them, however, if you don’t have "Show updates" checked in Add/Remove Programs.

  104. PatriotB says:

    Er, make that "only some Office security updates are *not* uninstallable" in my posting above.

  105. Xepol says:

    Ever since IE 7 came out, there are certain sites that IE doesn’t download from.  Obviously, the problem has been reduced, but I have found one very persistent case.  I bring it up, because as I view the headers, there doesn’t actually appear to be a "real" problem (read: spurious error message).

    Borland’s CodeCentral ALWAYS immediately fails when you try to download a file, it says "Internet Explorer was not able to open the Internet site.  The requested site is either unavailable or cannot be found. Please try again later."  Now, this is interesting because when I drop a logging proxy into the mix, the data is completely sent before the box appears.

    In the case of this URL,  we are talking about less than 10k.

    As I investigated the headers, I can not seem to find anything that is actually wrong.  If you guys get a chance to check it before you deliver the final IE, that would be really great, because I am concerned that an apparently valid transfer is being marked as failed for no adequate reason.  If the problem lies in IE, you guys can fix it easily I am sure.  If, however, there is something wrong with the CodeCentral reply, it would be nice to get details to be forwarded to them so that they fix it appropriately.

    No, I don’t work for Borland, I am just sick of having to fire up Firefox just to get a 10k file.

  106. DanielL says:

    RC3?  There is an IE7 RC3?  Why testing with RC1 then?

    Why so many bad comments about CSS?  Do we really have to worry?  Is the CSS up to date in IE7 or not?  Is it at a level comparable to FF, better or worse?  Tell me and I should be set for what to use.

  107. EricLaw [MSFT] says:

    @Benjamin Hawkes-Lewis: There’s a problem with the spam flagger for blog comments, and I suspect that excessive direct hyperlinks are to blame.  Sorry.

    @Xepol: This is a bug in Borland’s site.  See  The specific problem is that they return HTTP/206 in violation of the RFC.

    @Martin T: Yes, you can uninstall IE7 if you’d like.  Just use Add/Remove programs.

    @sibyl: See for some tricks to customize IE’s search box and menu.  We’re looking at more-complete customization for a future release.

  108. Tino Zijdel says:

    So I guess this is it, Microsoft is again going to release a product that is from a techical point of view mediocre at best and still holding back the web by 5 years or so.

    Luckily I’m too stumped having to work around IE6’s bugs and quirks for years and recently IE7’s bugs and quirks as well to be as sharp as I want to be so I’ll start this rant in a positive way by expressing my respect (and sympathy) for those who have worked on this product. It must be really hard to work for Microsoft and especially the IE-team: on the one side they have the ‘big bosses’ and the shareholders that don’t care for anything but release dates, money and market-share for keeping the lock-in on as many consumers as possible, and on the other side they have the developers (developers, developers!) that are screaming for standards-compliance. We all know which side will always win and if you are a member of the IE-team and actually care about standards-compliance that probably must be very frustrating. Probably Bad Agile…

    When Microsoft anounced that they were reformatting the IE-team to work on IE’s next version somewhere a year ago I was sceptic but did have a tiny shimmer of hope that IE7 would be a good step forward. Throughout the development of IE7 my hope got thinner and thinner and vanished completely when I tested RC1: IE7 is still as buggy and incompliant as IE6. Sure they made some marginal improvements having hacked around some commonly known CSS problems in IE6 and extending their CSS support a little but on the other hand this introduced new problems as well and some very fundamental CSS features are still lacking or plain buggy. Not to mention the fact that on other areas besides CSS there is almost nothing new or improved at all.

    It seems to me that it was clear from the start that IE7 was not intended to be a technological better product than IE6. The lack of feedback on bugreports and the ever recurring ‘we’ll consider that for a later version’ clearly demonstrates that. I know my rants over the past months here at IEBlog have been harsh at times, but me and others also provided a lot of code examples where IE7 still goes horribly wrong – things that at least should be right in a browser released in 2006. I even took the gamble of reporting (privately) an issue with IE’s cookie-handling that violates RFC2109 and poses a security-risk almost a month ago through Connect but haven’t had any feedback on that either. I am and have always been willing to help make IE7 a better product but it seems that help just isn’t wanted. I don’t know if that is because of incompetence, ignorance or just arrogance.

    I now just hope this comment will at least make some people at MS think and that they will put more effort into the next version and actually show their commitment at making IE more standards-compliant. I don’t see it in IE7 yet.

  109. aaa says:

    My IE7 just crashed in the first website I entered.

  110. James says:

    Pretty poor that you can’t run IE7 side by side with IE6. With the recommended workaround to run IE6 in Virtual PC? Riiight…

    Embedding IE into the OS so much looks like a pretty crap decision about now.

  111. Tino Zijdel says:

    James’ point is very valid: from a webdesigners point of view it is very inconvenient that there is no easy supported way to run IE6 and IE7 side-by-side. IE6 will still (unfortunately) be with us for a very long time (eg IE7 will not be available for win2k or below).

    For all other people asking about IE7’s standards-compliance: IE7 will still be the least dominor when it comes to supporting (some long-standing) standards and recommendations. It basically is a 2001 browser with a 2004 GUI and 2006 marketing. I’ll leave it to other people to call it what that means.

  112. PeteL's Blog says:

    It’s crazy, in the last 5 weeks, I’ve gone from being a tester in Visual Web Developer to a Product Manager

  113. Xepol says:

    @ErikLaw -> Thanks, I guess I just didn’t notice that.  However, it is complete partial data, so I’m not sure what the huge violation worth throwing out my download is worth…

    I’ll nag the guys in charge tho to get it in compliance!

  114. Xepol says:

    @EricLaw -> Sorry, misspelled your handle – the only excuse I can give is turkey poisoning as I attempt to digest my day-early Canadian Thanksgiving dinner.  

    Too all the Canadians out there, happy Thanksgiving – to the Americans, your turn is coming, don’t worry.

  115. markus says:

    I believe that ms is way to late with their browser, firefox still p0wnes ie and always will be

  116. Carol says:

    My system crashed after using IE7 for a couple of weeks. Driver wasn’t working.   During that time it was slow, IE would take a nap occasionally during use, etc.  So I uninstalled it and restored my system to about 3-4 weeks ago and now I’m fine.  Most of us out here are just everyday kind of people using the internet.  We don’t know all the little tricks of the trade and some of us are technologically challenged at the least.  Let all of your customers know when we can download and use it without a lot of problems.

  117. Xepol says:

    Now if only ExtremeTech quit treating IE7 like a pre-historic browser in the forums and gave us back the full editor!

  118. Will says:

    "someotherguy": If those are the only problems you’re seeing with IE, they should DEFINITELY ship it.

    Most of these fall into one of three buckets:

    1> Do not reproduce

    2> Incredibly trivial

    3> Incorrectly authored HTML

    4> Obvious workaround

    Nothing there is critical.

  119. Sarath says:

    The memory utilization of IE is really appreciated but really the IE is too slow comparing to Firefox (with/without plug-ins). This is from my own experience 🙁

  120. Paulo says:

    Guys, there are still problems to be solved, namely on the IDN domains rendering:

    – doesn’t work on ie7 (and works on all other browsers)

    – there are still adjustments to be made on the language character codes mix acceptance. An example: the € character. (zyyy…)


  121. says:

    We have been waiting for internationalized domain names for 5 years. This is it. Thank you.

  122. Will there be any changes in IE7’s client-side scripting? I have never worried about detecting browsers or versions before for anything other than using event.keyCode for JScript and event.which for JavaScript. Will this or any other client-side scripting be different than before?

  123. From the IE Blog is the following – we have all heard that IE7 is coming, but that day is almost upon

  124. NikolajW says:

    Efterhånden som vi nu nærmer os en færdig udgave af IE7 så bliver det også vigtigt at vi som udviklere

  125. Chrialex says:

    I used the beta of IE7, and I now have Vista RC1, soon to be RC2, and have not had any problems with it.  I like the version of IE7 that came with RC1, its not as resource hungry as previous versions.  I have the latest versions of Opera and Firefox and they both use more than IE7 for a change.  One thing that I dont like is the layout of the different bars at the top: add, then menu, then tab.  I would rather have the menu bar on top, add bar below that, and then the tab bar below that.  And the background color around the add bar is black, which is ‘different’. But its not that big of a deal.  Oh, and if you could also use widgets or add-ons like opera and firefox, that would make it complete.

  126. EricLaw [MSFT] says:

    @Paulo: I’m not sure I understand your claim.  IE7 will convert to, as required by the RFC.

    @njsokalski: Generally, the JScript model has not changed.  Neither of the checks you’ve mentioned should need an update.

    @Chrialex: See for a registry trick that puts the menu bar at the top.

  127. Nic Bedford says:

    I just finished installing Vista RC2 Build 5744, and IE7 can still not login to my Speedtouch Router, (see for other comments)

    Is this ever going to be fixed? Is it IE7 fault or Speedtouch firmware fault?

  128. rc says:

    It is obvious that Microsoft and IE team pursue their own goals which aren’t related to the goals and needs of both users and Web developers. MS never was going to release a good browser. MS never was going to release a W3C conforming browser. MS never was going to release a usable browser. So why do you continue claiming that MS hasn’t done it all? MS does what it wants to do, not what you expect, not what you need.

    A mocking "feedback" system clearly shows that MS doesn’t take an interest in any feedback and will continue to ignore all suggestions, reasonable or not. "It will be kept for future versions" really means "We don’t take your opinion into account".

  129. Flash says:

    IE7 is not a good predecessor for IE6 but it is a step in the right directions.

    Regardless that IE7 isn’t complaint with most of the existing web standards it is still a good opportunity to get users moving forward in browser technology.

    For those people who are complaining about thier websites being broken by new IE7:

    It’s your own fault!

    Those who have been using hacks and other tricks to emulate behaviors in IE6 are now paying the price. Although new quirky bugs have appeared "some" of the worst rendering issues have been fixed in IE7.

    If everyone followed the web standards (set by W3C) then your website should work in other alternative browers (like Opera and Firefox) and should also continue to work in IE7 (in theory).

    Although MS is ambitious to push this out in an automatic update they should really hang back for further user-end testing (yes, we all know there is going to be problems) and proceed to release it 6 months down the line.

    Although I am an idealist (as I am sure many good web developers are) getting users used to the new GUI on IE will beckon less problems in the future (the design is logical. Those who have been using new generation browsers like Firefox and Opera would agree).

    If the IE Team can deliver, in maybe a year or so time (through updates) IE7 could be made to be web complaint as most of the other browsers that already exist on the internet.

    This excites me as I am desperate to see the pains of IE6 go away as we move into a better, more convienent web browsing community.

  130. Ray Munro-Crump says:

    In all the betas released IE7 clashed with HP Director (The program that its scanners use) and HP Director just would not work. Uninsatlling IE7 let it work again. Anyone know if this glitch has been fixed?

  131. Mako says:

    At first I was really annoyed when I read about the changes but a quick check on some of the sites/rias I made during the last years showed that it’s suprisingly easy to fix most of the stuff that broke.

    Still it would be great if Microsoft could release a proper installer for IE 7 that doesn’t kill IE 6. At the moment you either need the earlier mentioned hack or a virtual machine to test your work. Why?

  132. kessa says:

    "IE7 Is Coming This Month…Are your parents ready?"

    Bloopy – You’ve got a great point here and one which I think Microsoft may have overlooked (or ignored)

    before I get onto the negative I just want to say that overall I’m not anti-microsoft (I’m probably the only one in our office3 who isn’t)

    However, most people who design / build for the web know that there are a few basic principles which you simply don’t break – and usability is one of them.

    For example: The file menu.

    For those of us who consider ourselves to be "tech savy", then moving the file menu is annoying, but we’ll probably get used to it.

    But for our mums, dads and any other silver surfers out there this is going to be a nightmare.

    One day they are happily surfing and they get a little message saying that windows is installing and updates – they continue blisfully unaware of what the update is (remember – they’re not "techies" so they won’t know about declining the upgrade)

    Next time they go to browse everything’s shifted – where’s my file menu gone!?!?

    WHY, OH WHY did you have to go and move such a fundamentally important user facility!?!

    I’m going to get SO many phone calls for help – THANKS MICROSOFT!?! (Not)

  133. Bert says:

    @ kessa

    Yes, it is a shame for some people that they are going to have to engage their brains and use a damn bit of initiative.  Did the human race become the most dominant species on the planet by evolution or whinging that they would like the planet to stop so they can get off?

    OK, so I’m being a little harsh but is this how you want computing to stay forever?  We have a nice little File, Edit, View,… menu and this is the way it will shall always be?!? Seriously?!  I seem to remember people whining about how DOS was much easier.  All you had to do was type "edit" and you had a text editor.  In Windows 1.x you had to look for a little picture and then click on it!  Then came along Windows 9x and they got rid of program manager and (grrrr!) you had to click on a menu structure.  Damn you MS why do you have to innovate!?!?

    Whilst I’m at it I really wish my car had one of those manual cranks at the front to start the engine.  These new fangled keys are just too flimsy and so easy to lose.

    Maybe people won’t like the new interface designs, but it’ll probably catch on.  Will the sacred cow that is Firefox ape these designs in 3.x.  Probably.  In fact there’s probably an add-onthemehack to do this right now….

    I’m sorry people, but suck it up and welcome to the future.  You might be in for a long ride…. :o)

  134. Igor says:

    just as predicted on

    Don’t be suprised if it is bundled with the November Hotfixes.

    direct link —>

  135. xfile says:

    I like IE except,

    (1) as many commented, unable to install 6 & 7 side-by-side making web development a big problem.  Please consider it again,

    (2) International domain name – finally works and happy 🙂  But please consider for retaining the domain name in the foreign language as Firefox and Opera do,

    (3) Menu – yes, please add back customization ASAP and what happened to "show history"?

    (4) Still can’t delete all history in address,

    (5) A wilde though – if 6 and 7 can’t install side-by-side, how about to make 7 to run in 6 mode? 😛 adding this special feature for developers?

    This month means – Oct.?  Wow!!!

  136. Sereby says:

    is this bug fixed in final release?:

    i have some folders in my favorites and if i have the IE opened a while i cannot reopen some of the folders! i have to restart the ie that it work again 🙁

    and i locked the favorites but its resizing ever time! its growing and growing! i have to resize it every time..

  137. Andreas says:

    What do you mean with "check if your page is ready for IE7 "??? A page does not need to be ready for IE7. IE7 hast to be ready for standard-comformant web-pages, not the other way around. Better fix the CSS-bugs before the release.

  138. Tim Weaver says:

    According to the IE blog we should be seeing IE 7 available this month: "The final release of IE7 is…

  139. MrBester says:

    "For those people who are complaining about thier websites being broken by new IE7:

    It’s your own fault!

    Those who have been using hacks and other tricks to emulate behaviors in IE6 are now paying the price."

    @ Flash: If there is a single site that I have made (that currently is W3C compliant, AAA rated and semantically coded) that fails to render properly in IE7 when it renders "correctly" in IE 6, 5.5 and possibly even 5.01 then I will forcibly ensure that any browser claiming to be IE7 will not receive styles, script or anything that would make the browsing experience remotely pleasant. I will also include a big fat paragraph (using deprecated tags like FONT becuase that is all it deserves) pointing out that the fact that I have invested a considerable amount of time in ensuring that the site was usable until this version came along and I have no intention of continuing the practise of bending over and parting the cheeks.

    However, I hope that this does not come to pass, as that will still entail hacking the sites. It would be easier to just ignore it, but all the "it’s an optional download" means nothing to the vast userbase that has WU autoinstall enabled. They will get IE7 the day it is pushed, and are most likely to be the ones who don’t know how to downgrade again, and also the most vocal when they can’t view their favourite sites.

  140. Dan says:

    Whats IE ? im defently not ready for any more unwanted microsoft blobware sence i dont use any.

    And id bet IE7 will be crawling with … things…

  141. Bert says:


    LOL!!  So you are going to lock out users of IE7?  I assume your websites are nothing more than tinpot personal websites featuring pictures of your dog then?  I mean they can’t be anything serious if you’re willing to lose visitors by not supporting their browser.  If you are a serious web developer then I hope your profits or the profits of your employer do not suffer too much.  

  142. El navegador Internet Explorer 7 saldra al publico este mes y se instalara via actualizaciones automaticas. Preparaos…

  143. Tim says:

    There have been a lot of comments indicating that if web developers had followed the rules then the IE7 would be a non-issue.

    This ignores two things:

    – web pages that followed the rules will not render in earlier versions of IE.  Developers are pragmatic and generated working pages rather than standards based (but non-working) pages.

    – automated authoring tools have been the worst about breaking the rules and generating non-compliant (but generally working) markup.  Often there was no good reason for the non-standard markup (especially from tools from MS), but if you wanted the productivity gains from the tool then you were stuck with the uglyness.

    So after 10 years of being forced to do the wrong thing, we are now being lectured about having done the wrong thing.

  144. MrBester says:

    "So you are going to lock out users of IE7?"

    @Bert: why not? It is no different from major banks locking out users who aren’t even on Windows (let alone using something other than IE) because they use IE specific code.

    Try explaining to some PHB why it will take even longer for a site to become live because you have to code for yet another browser (if it needs workarounds, it becomes equivalent to being another browser) when they’re already hacked off about how long it takes to fix for the browser on their desktop.

    Anyway, as I said, I hope (and fervently pray) that this isn’t going to be the case. From what I have read on this blog (and elsewhere) it seems likely that it will be business as usual, in that the older versions (which I have to support, corporate isn’t remotely guaranteed to be using IE7 for some considerable time) still have their hacking, but IE7 doesn’t need it.

    I don’t support IE/Mac whatsoever anymore as a) Microsoft don’t and b) it’s just too much hassle when you’ve got multiple versions on Windows to deal with already. Those users (and why wouldn’t they use Safari anyway?) get the same as Netscape 4 and Google; a valid, semantic yet unstyled page with no scripting.

    "So after 10 years of being forced to do the wrong thing, we are now being lectured about having done the wrong thing."

    QFT. Suddenly, we’re being painted as the bad guys, when it wasn’t our fault, but certainly our problem.

  145. Entro la fine di questo mese dovrebbe veder luce la release finale di Internet Explorer 7 prima come

  146. Robin says:

    "Those users (and why wouldn’t they use Safari anyway?)"

    Tell that to the publishing sector, who seem locked into Quark 4 and by association MacOS9 and Mac IE. Sob.

  147. uber1024 says:

    This will mark the time in which I officially became a Microsoft hater.  I don’t want IE 7.  I don’t care about IE.  Our servers are already running out of disk space because of all the garbage that gets installed on them with Automatic Updates.  I’m looking pretty stupid after defending MS business and technical practices over the past decade.

  148. Aedrin says:

    For all those "web coders" complaining about how they have yet another browser to support and fix for, how it is wrong that IE needs to bested with their websites.

    Grow up and do your job.

    If you had to spend so much time fixing your layouts for IE, then you need to learn more CSS and less hacks. The reason why MS has to ask everyone to test their websites is because the owners of them were stupid enough to put proprietary code in them and expect IE to respect those for eternity. Even though they are whining for IE to respect standards. Which is it that you want?

    If people took better care of their websites, they wouldn’t have to ask everyone to test them. The Web is a mess with a lot of websites that are so incorrect it is surprising they have worked until now.

    If only they would’ve made HTML require XML validation from the start, none of this would’ve happened. Browsers were too lenient on developers who couldn’t produce a proper line of HTML.

  149. Aedrin says:

    Those people that complain about having to be asked to test their websites (I can’t believe people complain about this):

    Remember that time when FireFox finally properly displayed all websites and didn’t require people to test their websites?

    Oh wait, that hasn’t happened yet. Right. So why are you complaining? Any program that is more than Hello World is going to have bugs. IE does, FireFox does, Linux does, Windows does, MacOS does.

    "So after 10 years of being forced to do the wrong thing, we are now being lectured about having done the wrong thing."

    And it’s about time. I’m glad people are being forced to validate their code better and hopefully they will stop using worthless tricks.

    I hope someone figures out a way to start over the internet, and actually start a Web 2.0. Not this cheap imitation 2.0 that blogs are supposed to be.

    @Tino Zijdel:

    Stop complaining. Your code is perfect? I didn’t think so. Stop bashing IE already. IE7 is a great leap forward in fixing this mess that people have created themself.

  150. Joost says:

    this is working in all browsers except for microsoft IE. even IE7 (as i saw on

    will you be fixing this? see to see my code is valid xhtml.

  151. Mike says:

    To answer your qwestion: no, I am not ready. But I guess I have no choice.

    Please use this blog to provide us with support on issues that will come up in IE7, like work arounds or alternatives etc.

  152. Joel says:

    Damn, there goes my idea of having a vacation this month!  I’m going to be glued to my desk, trying to workaroud all these bugs!  I can’t believe that your are planning to go live, with what is in RC1.  What a joke!  There are so many major bugs still outstanding!  If you are serious about this version going live, you *NEED* to give us more time to adjust our code to work with IE7.  Like most, I have been waiting for the ‘final’ RC release before wasting a second of my time doing any development for a moving target.

    Where is your QA Department? have they not been telling you that there are so many bugs still needing addressing?

    Yikes, Halloween month is going to be scary!

  153. Aedrin says:

    Actually I realized how amusing this is with all the people who will actually have to update their sites now.

    If only they wouldn’t have gone for the hacks and shortcuts.

  154. Michael says:

    UI Changes that seem to bother some folks and where to find them.

    1) History. You will find it by clicking the favorite’s button, favorites, RSS & history right there.

    2) Traditional menus. Even if don’t turn on the menu bar (right click on the tool bar and click menu bar to do so) the keyboard shortcuts still work. Alt-F for File anyone?

    3) Tabs – I like the way they work in IE better then FireFox, particularly the new tab function. The close button on the tab is also more intuitive. I hope FireFox adopts this convention.

    4) Customize – I agree here, this is not as good as it could be but then again it is pretty limited in FireFox too. You can unlock the toolbar and move most items around and for the most part customize what they contain. This is not new folks; it’s been part of Windows for a long time now. I wouldn’t be surprised if IE8 didn’t adopt skins.

    5) Compatibility – There is still much work to do here but it is moving in the right direction. Since I always test with IE & FireFox and WANT as many customers as possible I have not found one site I’ve made not render right in IE7 and I’ve been at it since 1994.

    OK, it’s not all good – there are definite issues with applications that use IE for functionality. One that is really bugging me is the Style Builder in Visual Studio. It is totally broken and is a real pain in the backside since no one at Microsoft wants to talk about it. Tip of the iceberg perhaps?

    Testing – Well having been a professional developer since the early 80’s I’ve seen time and time again folks treat it like a dirty word. Nothing new there. The web space is particularly bad at this as it is so easy to build and deploy that many developers are forced through bad management to ship now test later. But really folks, it’s time to stop with all the nonsense about testing. Better you do it then your customers – assuming you care about them. Yes, it would be very nice if you could run IE6 & 7 side by side but since this has never been possible it is highly unlikely it will be now.

  155. UnexpectedBill says:

    Well, congrats to the IE team–not only for getting their act together with the IE browser (at least to a point) but also for publishing a blog about the development of the browser. It’s been very interesting reading over time, and it really doesn’t seem like that long ago that IE7 was "a distant light". Now here it is on the verge of release…

    I don’t think that I’ll make the upgrade immediately, due to many of the same reasons that other posters have mentioned. But I will be testing it.

    One thing I’m really hoping to see–please, please, please make the all toolbars freely and completely adjustable in the Windows XP version of Internet Explorer 7. I don’t like the presence of the address bar above all else and not having any way to move it.

  156. Avatar says:

    Is anyone going to reply/take into account all these comments?

  157. cj says:

    i’d also like to put my vote in for changing the way the browser looks.  i know you have usability people working on it, but it’s very confusing to me.  too many of my usual haunts are compressed or deleted.

    besides never remember which place my menus moved to, i’m also not able to shove all of the stuff together on one line any more so that i can maximize the height of my screen.  being able to put all of those bars and whatnot on one line was a *huge* plus for me.  i really don’t like how i’m forced to have everything on different lines.  do you realize how much space people lose on their 800×600 browser windows?

  158. Ice_Blade says:

    Wow, First we webdevelopers are required to use non-valid code and hacks to get a site to look correct (Which FF and opera etc do automatically)

    We have to have special css styles for IE 6 and 5.5 and 5.

    Now we (all webdevs) have to go and check the entire web and change millions of websites to be able to tell the difference between yet another version of IE (which is still not 100% CSS compliant (see lists of bugs above)) and still requires some hacks)

    The website now has to check whether the user is using a ‘normal’ browser or IE, and then check which version of IE its client uses to be see Which hacks are needed.

    Either write a browser that doesn’t need ANY hacks to show a website correctly, or create a ‘better’ browser that has BACKWARDS COMPATIBILITY for the crap you required us to put in our sites in the first place.

    Better yet, add a ‘dev’ mode so that webdevelopers can check a site for warnings and errors which occur in IE. A page might be XHTML valid, but IE will still render it incorrectly. Have it warn the developer for possible problems in the code…

  159. =jon= says:

    Are we ready?

    Are 4 year that we are ready…

    Must be IE7 compatible with my site, no reverse?! Or not?

    My web site already ok under FireFox, for examples, so I think that IE7 must be compatible with IT!!

  160. Luke Rumley says:

    I have been trying to find a place to post a site that no longer works in IE7, though it worked in IE7 beta 2, IE6, Opera 9, Firefox 1.5, Safari, etc. (navbar does not work in IE7 RC1)

    I tried the User Agent change (even though I am not doing any browser detection), and I tried turning off the javascript and the CSS hack for Mac IE that I am using. No luck. They are both back on now…any ideas?


  161. Aedrin says:

    "Wow, First we webdevelopers are required to use non-valid code and hacks to get a site to look correct"

    Required? Who put that gun against your head?

    I use 0 hacks and 0 non-valid code and I do fine. Who’s forcing you?

  162. Anonymous says:

    The final release of IE7 is fast approaching and I mean really fast and will be delivered to customers via Automatic Updates a few weeks after its available for download.

  163. Michel Azevedo says:

    how can i disable IE 7 "Shrink to Fit" feature. I have a application where i call window.print() and ie resize the page. Is possible change page scale via script??

    that’s my problem with IE 7. Firefox behave ok.

  164. MiTrastero says:

    [IMGLEFT=/areax/homes/blog/IE7.png] Parece estar confirmado que la liberación de la versión 7 de Internet Explorer [URL=http:/ …

  165. Todd says:

    Obviously that comes from someone who never created a web page in his life.

    The HACKS they are referring to ARE the CSS and javscript needed to make various browsers render the same way. For example, try to make any version of IE prior to IE7 display a transparent PNG. It can’t be done without some javascript/CSS/DXTransform magic, because the browser doesn’t support it out the box.

    Then again, just to be fair, try to make FireFox display WebPart menus correctly.

    Amazing that you can use the words "grow up" and and D-Word in the same sentence. Graduate high school first before you start spamming people who are doing their jobs.

  166. Pinner says:

    Will IE7 fix the current bug with innerHTML on select option elements?

  167. The IE team announced that the RTM version of IE7 will be release this month. We’ve blogged off and on

  168. Aedrin says:

    If your source of information is a search engine like Google then you’re not going to convince anyone.

    I don’t think Microsoft is demanding everyone conform to their standards. They are themselves working to support all standards but this requires a lot of work. It’s not as easy as FireFox had it by just using an existing rendering engine.

    Hacks are pointless and this just proves how bad it is to use them. If you can’t find a solution using your existing tools, do you break them and try to make them work differently?

    Using hacks is just like how Microsoft started using proprietary stuff. Yet it is okay for people to use them, but not Microsoft?


    The D-word?

    I’ve been creating websites for several years and I do fine without hacks. Very mature response though.

  169. Mark S. says:

    Will WIE7 break HP Photo & Imaging Director for my HP ScanJet 2300c?  Because I use this program very often and it would be really bad if it stopped working…

  170. Seriously, we need to test for compability? We need to debug and find the bugs on our own? We need to support yet another browser?

    Why is this Microsoft?

    As far as I know the standards have envolved but they keep backward-compability… This means that if you did support THE STANDARDS before we won’t need to test and fix things. We won’t need to support another browser because IE6 will stay here for a long time.

    From what I’ve tested, you’re NOT ready and you don’t yet fully support the standards. Go back and fix it first.

  171. If you have been following the IE blog and Sandi's blog you would know that IE7 is going to be shipping

  172. Michael says:

    Aedrin – here here. I get so tired of reading all the non-helpful replies. I’m looking for solutions, not pontification. Please keep that part to yourself folks.

    Regarding the d-word, I think it was developer. Might be wrong but it was the only d-word used in the same reply as "grow up".

    It would be to everyones benefit – including Microsoft’s, to not put in support for the sins of the past. It will just make IE more difficult to support and create more opportunities for trouble in the future.

    Has anyone ever created a site that compares broswer functionality in the form of a chart?

  173. Adam says:

    I’ve use IE 7.0 RC1 XP version the only thing that’s missing now is the ability for a limited account to install active x on Window XP Limited account. I think that IE 7.0 Vista version has the capability to install active x on limited account. are there any talk about adding that on Window XP Limited Account?

  174. Rick says:

    @goose you are such a troll, there is no way on this planet, that you got spyware from Firefox or Safari.  Nice try, you dug your own hole on that line alone.

  175. Bugsy says:

    @goose is really smart I just got SPYWARE from this GOPHER site, dont use LINX I just got infected with a bad virus on my machiine and now I get kernel panic?! Hows come IE7 dont work anymore with new WINE? and when they going to releaese this version for MAC (ie4 too old!)

  176. Aedrin says:


    I believe there are several sites. But they come with the obvious bias towards anything non IE 🙂

  177. IE7 Is Coming This Month…Are you Ready?

  178. ieblog says:

    @ Jeff Luckett

    Please send an email to the IE Blog describing your issue with IE7 and Authorware 6.5 so that we may further investigate your issue.

  179. none says:

    is IE7 still set up to recognize and refuse operating on websites with expired certificates?

    If so, does this mean microsoft will be updating Windows Update since after all the activeX certificate expired more than a year ago.

  180. The IE team have announced that the next version of IE will be out this month (although an exact date

  181. nephre says:

    Why should we prepare our websites for your browser? When will Microsoft eventually create a browser that will respect web standards?

  182. EricLaw [MSFT] says:

    @Nic Bedford: The Thomson folks say they have updated the SpeedTouch firmware to address the Digest auth issue.  Unfortunately, I don’t have one of these devices to verify.

    @xfile: IE will display IDN names in their native form if the user has the correct languages specified in the "Languages" section of Internet Options.  Showing PunyCode prevents spoofing for other worldwide locales.

  183. Tino Zijdel says:


    "Stop complaining. Your code is perfect? I didn’t think so."

    How would you know?

    "Stop bashing IE already. IE7 is a great leap forward in fixing this mess that people have created themself."

    I’m not bashing but mere criticizing and I think I have backed that up with enough examples in my previous posts. I am still very willing to give many more examples of things that are still horribly wrong or lacking in IE’s implementations of CSS, JS, DOM, HTML, HTTP and whatmore if I would have the feeling that the IE-team would actually listen and do something with it (and I mean do something with it now and not ‘consider it for a next release’  maybe 18 months or more from now).

    IE7 isn’t really that great a leap if you look at what has been done and compare it to what hasn’t been done in terms of standards-compliance.

  184. Michel Azevedo says:

    how can i disable IE 7 "Shrink to Fit" feature. I have a application where i call window.print() and ie resize the page. Is possible change page scale via script??

    that’s my problem with IE 7. Firefox behave ok.

  185. nate says:

    here’s an idea – how about you get your product up to global development standards, and our sites will work. If my standards compliant site breaks (after all, aren’t standards there to ensure functionality across platforms?) then it is YOUR fault, not mine.

    friggin’ microsoft

  186. EricLaw [MSFT] says:

    @Tino Zijdel: I’d love to hear about your HTTP concerns.  Ericlaw at microsoft dot com.  Thanks!

  187. brett says:

    its a fact of life, no, that things change? I’m used to it.  Fact of life that while MS can listen to comments here, they are not likely to change their release plans much, if at all – so be ready for some home user accepting IE7 on their home PC, and make your site handle that.  Anyone who has a website that verifies browser versioning may have a specific list of browsers that may not include IE7 – that’s the minimum I guess you’ll have to do…. but do it, or your customers will get peeved at you for not giving them an acceptable experience.  It’s no longer the challenge and cost it once was to change banks, move mortgages, buy coffee bean from another internet vendor (the list goes on ad-infintum) so being prepared seems to be in your own best interest.

  188. zzorio says:

    I suggest to put this legend in no IE7 compatible websites:

    "I you cannot see this site is because you have installed a piece of softawe not compatible with actual websites. Just unistall it to solve this problem"

  189. thehailo says:

    I am shocked and greatly disappointed that anyone would ever put so much emphasis on web designers modifying their website to work with a browser.

    The very idea of the World Wide Web is a standard forum for all. The thought that testing and tools must be provided is insane. Any given standards compliant site should work perfectly well for all web browsers, or equally broken for all. The notion and effort put forth to “prepare” the world for IE, indicating that sites require modification, shows that IE7 along with the culture and design principals around it are horrendously broken.

    Congratulations for MS on finally getting another release out the door, but I’ll anxiously await Firefox 2.0 and continue using FF1.5 and Konqueror in the mean time.

  190. Michael says:

    We all need a bit of perspective here. Perhaps some of you are new to this stuff.

    I work to real world metrics which means I live by my server logs. I make sure that my top priority on the public sites I’m responsible for is the top platforms and browsers that visit my sites work without question which is not to say I don’t make changes along the way to support the others, I do. From 1998 until just the last year or so, that was by far some flavor of Windows with whatever was the current version of IE (unless the site was specifically targeting a non-Windows audience). Through the most of this decade that has been a Windows XP box with IE6. You add up all the Linux/Mac/Opera/Netscape/Mozilla/Lynx/WebTV combinations and they still only total a small fraction of the total number – again, until just this last year.

    While there is a definite growing crowd of adopters for Mozilla FireFox – a fine product BTW, IE6 is still the de facto standard based on the numbers – and it’s not likely to change any time soon. Most technologists forget that it’s hard enough to get "ordinary folks" to update their anti-virus definitions on a regular basis or keep their inboxes under quota, never mind go out and download a new browser. I have several clients that don’t even know for sure what the browser is and could care less. To them it’s the Internet icon or, more amusing, it’s the Google window (for those who have set Google as their home page). Please remember this before you start smacking folks around for doing their job and targeting their audience.

    How many of you remember the browser wars? IE was not the only browser to introduce non-standard tags or offer features that were not per W3C standards or introduce bugs that needed a workaround. Anyone remember trying to nest tables in Netscape or put links in table cells? Remember how Netscape 4 would crash when trying to run Java apps? Both Netscape and IE did whatever they pleased to keep their place in the market. I also remember that Netscape was the company that introduced the idea of HTML, JavaScript enabled email. Microsoft on the other hand wanted to use a variation of RTF. After taking much heat for their proprietary format, they caved in and offered HTML support in their email. In retrospect I wish they had won that battle as we would not have needed to consider the inbox a target, which for those of us that have used email since the mid 80’s, always found that absurd. It was the gift that kept giving for a very long time – thanks!

    Anyway, for those complaining that their older IE6 specific sites might need testing and updating, there is no point in complaining because in the end you will have to do it. I sincerely hope that if IE7 and beyond continue in the direction they are going that they become standards compliant and do cave in and keep supporting the old quirks. It will be better for everyone if they don’t so our sites can all be browser agnostic.

  191. Roger says:

    @Rick and figgy

    Of course goose is jesting you morons 😉

  192. Tommy K says:

    To Michael.

    While reading most of the comments here it seems they imply standard conforming web design could not work in IE. This is false, but the truth is: your designs are very limited.

    I think the problem of "blue e" = Internet is well-known.

    Although Netscape introduced many non-standards to the web, Netscape4 is dead now. !Completely!

    What Netscape 6 and so on are, is just a new layout engine keeping the design to be familiar. This engine does not include most of NN4 non-standard code, if at all?

    IE on the other hand is still based on Mosaic. As long as this won’t change IE can’t become a reliable product.

  193. Michael says:

    Officially it’s based on Spyglass which was in itself based on Mosaic. I have fond memories of Mosaic as Mosaic for x-windows on Solaris was the first browser I ever wrote for. That was cutting edge!!!

  194. xfile says:

    "I have several clients that don’t even know for sure what the browser is and could care less. To them it’s the Internet icon or, more amusing, it’s the Google window (for those who have set Google as their home page)." – This is so true for oridinary people.

    The only thing that I am not comfortable with IE – if this is true, is heavily depened on CSS for web development in the future.

    Of course, blame for not using and demand to use CSS for professional web developer could be justified, but remember, web development is NOT just for professional web developers now.

    Many office workers, pop and mom stores, students, SOHOs, and so on are developing personal or small-sized e-comm stores, and it’s not really fair to ask them to learn CSS as many of them just use WYSIWUG editorz.

    I got the feelings that the new trend for using CSS-based web developing strategy will cause resentment fron oridianry folks.

    I do wish MS browser and development tool teams can always remeber those oridianry folks are mostly using their products, and please leave some rooms for them by not trying to convert them into "professional programmers".

    Please remember (for all technie fans) that it’s "easy-to-use" not "standards" nor "technologies" that rescued the computer industry and Internet from being abandoned by the regular folks.

    I won’t be surprised to see many folks simply abandoning doing the web site thing if it became a "professional" skill.

  195. gigglesworth says:

    >>>The final release of IE7 is fast approaching … and I mean really fast … and will be delivered to customers via Automatic Updates a few weeks after it’s available for download.<<<

    What? So suddenly? "a few weeks" is NOT enough lead time.

    If I understand correctly:

    – A voluntary soft launch of IE 7 is scheduled "real soon now". This is great– upgrades of this magnitude should be handled by volunteers first.

    – Microsoft will be pushing IE7 out to all Windows workstations and home computers within the next few weeks, which will effectively depricate IE6.

    This news is a little sudden. When depricating an old product, companies should usually give us advanced notice of 6-months or more.

    My web-based business is busy working on our own products— not reading MSDN blogs.

    We made the assumption that the upgrade from IE6 -> IE7 would be more gradual– like the upgrade if IE5 -> IE6 , or MS Office 2000 -> MS Office 2003.

    If IE doesn’t work 99.9% of the time, this will be a frustrating upgrade for web users and web businesses alike.

  196. Hi!

    So it will be the final version released tomorrow ?

    I think IE7 team must start to work in new upgrades, with more standard compliant. Opera & Firefox still the best ones for web.

  197. Michael says:

    "This news is a little sudden. When depricating an old product, companies should usually give us advanced notice of 6-months or more."

    To gigglesworth – This release has been coming now since 3rd quarter 2005. Beta-1, 2, 3 & RC1 releases throughout the last year – only 1 of which was not to the public. I agree the RC1 to RTM span seems a bit short but really, it has been a long time coming. Do yourself a favor and download a copy and start evaluating it now so if there is any problems with your tools you won’t be blind-sided.

    BTW: It works just fine. 1st time ever that I’ve recomended to my IE clients they install a beta product from MS on production PCs.

  198. xfile says:

    "If IE doesn’t work 99.9% of the time, this will be a frustrating upgrade for web users and web businesses alike." – I have the same concerns as you’re and that’s why I am here after learning IE is soon to be released.

    I’ve installed RC1, and seems everything is ok at this point for our site mixing with ASP, PHP, and HTML pages – knock 3 times.

    The overall loading is faster but I am still looking for any possible scenarios for incompatability, and if there is any, it could be a big problem for us since we don’t really know how to work with it.

    Our problems is using mixed tools (Dreamweaver and FP) and mixed CSS templates (provided by various designers), custom layouts, and embeded shopping car functionalities.

  199. gigglesworth says:

    >>>I agree the RC1 to RTM span seems a bit short but really, it has been a long time coming.<<<

    I realize that IE7 has been in a testing phase for quite some time– so I’m not completely ignorant 😉

    However, I only just now found out that MS will be rolling out IE7 via "Windows Update" in a few weeks. e.g. This rollout will effectively be a major, mandatory upgrade to millions of computers.

    I suspect most web-businesses don’t read the MSDN blog, and most of us were unaware of this agressive rollout schedule until today. Sure, we knew IE7 was coming sometime this year and we’ve run some tests– but little did we know that we need to be fully IE7-compliant in a few weeks.

    I’m fine with MS pushing IE7 out to computers in a year or so, after it’s been tested in the real world for a while.

    But 3 weeks of real-world testing with real-world users, and then release it? That’s insane– good solid development shops will experience major bugs with a schedule like that, and Microsoft produces buggier software then many other businesses.

    This schedule is going to cause many headaches.

  200. Michael says:

    To gigglesworth –

    Sorry – I wasn’t implying you were ignorant.

    "I suspect most web-businesses don’t read the MSDN blog…"

    I would agree but this blog is by no means the only news channel on IE development. As to the specific comment – I guess it would depend on what the web-business did. If you are a development house then it is your business to know what is coming.

    As to rolling out the update as a mandatory update, MS will make it possible to block the update. I’m not sure if that is only for corporate clients on SMS or if that can be done at the end user level. I’ll see what I can find out about that and report back…

  201. Victor says:

    I’ll skip my 75-100 bug reports, that haven’t been addressed, to focus in on the ones that count.

    1.) The MENU/TOOLBARS have to be moveable.  I seriously expect this to be available in your final release.  This isn’t a nice to have, it is a "you will look like the laughing stock" if it is not there.

    2.) Fix the horrible graphical stretching that occurs on 17character plus buttons in IE.  It looks pathetic, and you’ve known about it for over 5 years.

    3.) Button needs fixing. If the value attribute is present, and != ”, then submit it, *NOT* the innerHTML… come on, this is so 1994.

    4.) Minimum width on dialogs.  You have seriously messed this one up. There are no words to describe this level of backwards programming.

    5.) prompt() calls are now blocked.  They break my site now.  I will be putting in a "Download a real browser" link on my pages if this kind of crap is to continue.

    6.) Move all the garbage icons off the tab row. (EVERY LAST ONE OF THEM!) The TAB ROW, is FOR TABS.  If you don’t fix this, can you at least make the tabs in my MSN toolbar work again? They were *MUCH* better.

    7.) Full screen. What’s up with that?!

    8.) Printing. Have you guys tried to print with that?  Notice how all the print outs look horrible?

    I do not look forward to this release, it will be an I.T. Departments nightmare.  We are going to roll it out, then users are going to tell us to roll it back. What a waste.

  202. Gille says:

    So at 5:40pm on a friday, of a long weekend, you tell us that IE7 is going final this month!!!!

    Are you serious!

    In the stock market world, if you want to bury news, that you know the press is going to jump on you for, you release late on Friday., is that the plan here too? Hope that the developers are calmed down by Monday/Tuesday?

    I’m not. I’m fuming mad!  Where are the bug fixes you promised in the last 2 chats?

    What is in the final, that isn’t in RC1?

    Where’s the changelog?

    What the _________?!?!?!

    I would love to have audio on the chats.  Then, maybe then, you would understand how pi$$ed the developer community is about this.

  203. Michael says:

    About Automatic Updates:

    Contrary to what Microsoft would like you to do; with the exception of the most inexperienced computer users, I always recommend turning off automatic updates. Set it to instead download and notify – not install. The service will download the updates and then notify you they are ready to install. You choose what gets installed and you do it when it’s convienient for you.

    IE7 is not the only potential problem auto-updates can bring you. Poorly tested patches can create far more trouble as they can make very subtle changes that you may not notice for a while and not immediately associate with a patch.

    For information on a more automated approach to blocking IE7 from auto-updating:

  204. 英語版の話ですが。元ネタは、IEBlog。 The final release of IE7 is fast approaching … and I mean really fast … and will be delivered to customers via Automatic Updates a few weeks after it’s available for download. We want to ensure that you are ready a

  205. Michael says:

    To Victor –

    I hope this helps.

    To move your tool & menu bars around, right click on the blank space and uncheck lock the toolbars. You can then move most of them around and slide/size them to your pleasure.

    You are absolutely right though about the command bar on the tab line. You need to be able to move or turn off this one. My solution was to take off all the the buttons I don’t want and then slide and lock it the way to the right.

    What is wrong with the full screen option? Works just like it always has. Press F11.

    Printing – Shrink to fit may be what is messing with you. Your mileage will vary depending on the printer used and the DPI setting. Web pages are not for the most part designed to be printed. Wide pages especially so. The wider the page the more compressed it will be. Is this what you are referring to? Still beats the way it used to cut off the right side.

    I too have posted many bug reports both through official channels as well as slipped in to my bug reports in testing Vista. To date none have been addressed. Broken features in Visual Studio where IE dependency is at play are the most annoying to me as you’d think their premier development tool and their latest browser would be happy together via internal dog fooding at MS.


  206. If you have been reading the news you would of noticed the post from the IE Team, that Internet Explorer

  207. Michael says:

    and yes, where is the change log???

  208. Adam says:

    What happen if the user is log in with Limited Account and IE7 is available. does the limited account user get notified or is the

    notification disabled on this account?

  209. Michael says:

    If you don’t like IE7, wait till you see IIS7! You might as well forget what you’ve learned over the last 8+ years about IIS. IE7 is a joy compared to this.

  210. John Holder says:


  211. Bruce says:

    Team:  One thing I’ve noticed about IE7 (RC1) is that it seems to change the security rules for IIS and how it works with Front Page.  Instead of setting the "anonymous" access logon to IUSR <machine> – I’m having to set it to a different account to get FrontPage to administer it.  Once past that, it seems to work OK until I try to use some of the "Web Bot" components like the Media Player plugin – and it seems to break things like the photo gallery.  None of these are big things in and of themselves, but until they are corrected I can’t move forward to IE7 – as much as I’d like to.

  212. hunvreus says:

    Isn’t that Microsoft who uses the slogan "People-ready" ? Are you ?

  213. Le blog de l’équipe d’Internet Explorer précise, en anglais, les outils disponibles pour préparer l’arrivée

  214. Om Prakash says:

    There were problem in IE6 when cursor =hand or pointer.Is it solved in IE7.

  215. derry says:

    oh, that means that it’s the time when we’re looking forward to the sp1 for IE7…

  216. hAl says:


    > 5.) prompt() calls are now blocked.  They break my site now.  

    > I will be putting in a "Download a real browser" link on

    > my pages if this kind of crap is to continue.

    Try making a "real website". Using the prompt calls in a site makes sites look like a joke. Popping up windows to ask for input or give them popup alerts is just a big nono in modern webdesign.

  217. It’s nice to be use and Installation

  218. Hm. Another NON-Open-Standard Tool from M$! When do they understand that Open Standards are mandatory and people want to be in control of their information themselves?

    We will increase the volume of Firefox! World Domination with Free and Open Software, so that my neigbour can also afford a computer with a secure OS!

  219. Le blog d’IE a annoncé vendredi dernier que Internet Explorer 7, version finale, serait disponible ce…

  220. javier gomez says:

    I Think the question is exactly the inverse:

    Are IE7 Ready for our sites & meet web standards?.

    Acid Test passed? Security Ok ? W3C Standards?.

    We are waiting….

  221. xfile says:

    To Code is poetry:

    Oui, in these few days.

  222. Nic Bedford says:

    @Eric Law

    ref: Speedtouch, thanks for the info Eric, i guess i’ll have to wait for them to release the updated firmware. The Speedtouch UK website is still showing firmware 6.1 for my Speedtouch 716WL, which is the same version it already has (and that fails auth with IE7)

  223. Crewcut says:

    Forcing myself to code according to W3C standards finally pays off and will silence all those people who mocked me in the past for being so strict about coding.

    Already tested my websites and they all look good in IE7, just like they did in IE6 btw, since I always refused to use hacks, quircks and browser specific nonsense.

    So all in all I am a happy person 🙂

    And for those who don’t know: Microsoft is part of W3C too.

  224. xfile says:


    Can anyone kindly tell me what is "hacks" and "quircks" in web development?

    I haven’t heard about it until recently when the new IE is about to be released.

    Thanks in advance.

  225. str1der says:

    Many people here claim that IE7 should work with the internet and we shouldnt make the internet work with IE7.

    Although this sounds reasonable, unfortunately there has been a lot of web development in the past only tested with IE which was letting pages that violate web standards to appear OK on IE.

    If this new version is now more strict with standards I dont mind some web sites that use crappy code to have to be redisigned.

    But I wouldn’t use IE as a means of testing a website because a future version of IE could easily render my standard incomplient site (which could work with IE7) useless.

    I would therefore recommend using the w3c validator against any site that I would built to ensure that it would work with ANY browser.

  226. According to the latest information, IE7 will be shipped this month. But before it&#39;s being shipped

  227. jared says:

    With so many tools to make sure your current applications will work with IE 7, I’m convinced that this is a quality Microsoft product!




  228. Tim Cuthill says:

    Anybody else out there got an HP scanner? One of the things that definately does not work with IE7 RC1 is the currently supplied HP software suite. Apparently they’re "…working with Microsoft to resolve this". Presumably this translates as issuing threats of legal action if MS ship "as is" and being told to get knotted as it’s been going on for a while now.

    Shame really as I rather like IE7 and I don’t think it’s the browser’s fault. Anyone who writes commercial code under .NET 1.1 deserves everything they get in my book, but I can’t see MS using *that* as an excuse :-}

  229. Theo Coolen says:

    Rightnow I am testing IE7 RC1.


    When I am installing IE7 RC1 on a XP Pro SP2 client or W2k3 SP1 server I noticed that the installation is validating my copy of windows.

    I wonder if we can disable this check because when I have thousends of Windows XP SP2 clients (volume licensing) we are not waiting for some validation process.


    A. Does this installation/validation process depends on a Internet connection?

    B. If not (a) Can we disable this validating process for volume licensed installations (Windows XP SP2 and W2k3 SP1) Is there some kind of installation process option to disable this and continue the installation proces of IE7?

    B. Depends on A. Will we get some volume licensing version of IE7 standalone for Enterprise users?

    C. If there is no connection to the internet at installation time does the installation process still continue or will it crash?

    I ask this because because not all of out customers do have Internet access at installation time and we would like to install IE7 by using SMS or whatever.

  230. Theo Coolen says:

    A. Can you give us the exact release date of IE7?

    B. Can you tell me exactly when IE7 is released as an High priority update after the release of IE7 for download?

    We want exact data and not some indication.

  231. Theo Coolen says:

    I noticed differences in the way Microsoft is advising us.

    The checklist on url: (For users, developers / webdevelopers and It Pro’s)

    is different as what you advise here in this IEBLog.

    Why dont you assimilate this info into the checklist as mentioned before?

  232. Oneda says:

    A Microsoft anunciou que a vers&atilde;o final do Internet Explorer 7 ser&aacute; lan&ccedil;ada ainda

  233. It is easy. I’ll write in my page something like "If you find this an ugly page it’s because you are using IE7. Dont’t use that. Use firefox"

  234. You’ve been kicked (a good thing) – Trackback from

  235. Mark says:

    I just run multiple installs of XP Pro using Parallels Desktop on a Macbook Pro. One VM of windows for each browser 4.x – 7. Quick, easy, completely functional. Problem solved.

  236. Ivan Zhekov says:

    i am sort of web developer. i mainly do css and xslt transformations. and IE has always been a pain in you-know-where.

    i downloaded the RC1 gave it a try and i must admit i am not 100% satisfied. still there are bugs regarding floating and backgrounds as well as some more.

    i only hope that via automatic updates browsers will recieve not only security updates, but standart-related bug fixes too.

    othewise i have no use for IE7.

  237. IE7が今月リリースされるようです。 IE7Blogにはこんなタイトルの記事が・…

  238. Internet Explorer 7 represents a much improved browser when compared to IE 6. In beta testing this over

  239. Internet Explorer 7 represents a much improved browser when compared to IE 6. In beta testing this over

  240. Aedrin says:


    "Can anyone kindly tell me what is "hacks" and "quircks" in web development?"

    It is when web ‘developers’ use proprietary CSS/HTML to make a certain web browser do something different from others.

    It is a bad practice because every time a new browser is released (not just IE) websites will break and soon the makers of these browsers will have to accomodate to these hacks (people are already asking for this).

    I hope that people will stop using hacks. We can’t keep on supporting Netscape 1.0 and IE 0.5. The internet is a dynamic resource that should not be halted by ancient software that 50 users out there have installed.

  241. Jerry Macy says:

    I have been using IE7 since the first beta came out and the last version has been the best.  I have had no problems with any other product.

    Let her come!!

  242. says:

    Na oficiálnom blogu IE 7 sa objavila info, že finálna, non- beta verzia Internet Exploreru 7 bude uvolnená

  243. yes, IE7 has been a big pain!! things dont work fine and its like testing all apps/websites on another (third) browser…

  244. Na ofici&aacute;lnom blogu IE 7 sa objavila info, že fin&aacute;lna, non- beta verzia Internet Exploreru

  245. Steve Levin says:

    Hi, can someone please address the problem with IE 7 in that you can not move toolbars and reposition them?  While the new interface is streamlined, that is defeated with the inability to reposition toolbars. McAfee SiteAdvisor for example. If you install that on IE 7 it creates a whole new toolbar that cannot be moved. Please address it. Thank you

  246. We are ready and we want IE 7 out there as fast as possible since it loads our page in a split second compared to IE6 because of png alpha blending. IE7 supports it out of the box with no extra filtering needed and it is a blessing. Finally IE has catched up to Firefox, Opera and Safari. Get it out there ASAP, and by force!

  247. Chris Child says: does not work in IE7, well it loads, but after clicking on a wink or the like, it all goes down hill. pages dont load like they should. Also the phone site 02 loads, and you can login. But if you try and check your bill and the like, it just wont load the page. Both websites run in IE6 with no problems. from Chris Child,

  248. As you can see from the post on the IE team blog IE7 is headed for final release shortly. It’s fun reading

  249. Daniel says:

    I’m working in a school, and IE7 is not compatible with EXCHANGE SERVER 2003.  When we click on "Reply" or "Répondre" (on the French version", we can’t write text in the text box.

  250. Helena says:

    IE7 zoom facility is *still* not working properly far as I can see – it doesn’t zoom background images on the body element which can really mess up a site.

    Very irritating.

  251. Chris Case says:

    Funny, after reading the first third of the messages here, and reading all the material about making sure my website is ready fr IE7, I figured I was doomed. Any browser that says, "You may need to fix your site for this browser" can’t possibly work with my 100% w3c standard site… or can it? HUZZAH! IE7 renders my site perfectly. I took screenshots of IE7 RC1 and Firefox 2.0 RC2, and the site rendering is a duplicate, to the pixel.I’m rather impressed, guys. We’ve actually taken IE7 off our blacklist. (Which had been all IE versions.) IE6 doesn’t even pretend to render the site (for the longest time it just tried downloading the site as a file, since we use XHTML… o.O) now that we’re telling it we’re just using plain html, it shows some of the elements that were on the page… but it’s like my site was throw in a blender. IE7, on the otherhand, works 100%. I’m really impressed. good job, guys!

  252. jo says:

    are you ready??

    ie7 must be ready!!!!

  253. Tjerk says:

    Why the hell do we have to test the page on IE7, i work conform the standards from the w3c, this made my site work in Firefox and Opera without significant problems.

    And another strange thing: why can’t you easyliy run an instance of IE6 and IE7 side by side? Is it again baked into the OS?

    Strange, anyways i reccomend firefox.

  254. ihor says:

    jo, i think u are right!

    we are waiting IE7…

    But, may be, it’ll be good 😉

    P.S. Is here someone from USSR? :))


  255. Harry Richter says:

    It was great fun, reading all those comments on what has not been fixed in IE7, and on how people should use some other viewer to display their webpages.

    I am writing code for webpages as part of my job, mainly for one big customer. My approach was to write completely W3C compliant code, and see what happens. Well let’s see the outcome:

    IE6: displays as expected

    FF 1.0 to 1.5: rendering buggy, some things missing

    IE7: displays OK

    FF 2: with two small exception renders OK

    Now what do we learn from that. Other people have made other experiences, and I believe them, when they say they did. It comes down to the code. NO browser is completely W3C compliant. Depending on what you use in your code, the outcome will be one or the other. It is good, that MS is being asked to include even more standard compliance, and all the same effort should be undertaken by the other browser devs. Then, and only then will we have a browser-agnostic web. Until then, I, like most of the sane web-devs, will live by the server-logs, and as long as IE produces 80% of my pageviews, IE will be the standard to which I work. And for the 20% that see buggy rendering, I will have a link prepared to download IE7, and tell the audience to use a browser, that is as buggy as all the others, but displays my pages correctly.

    To the IE dev team: You’ve done a very good job, and I want you to know, that at least some of the people out there appreciate your work.



  256. Robin Capper says:

    Is IE7 ready? From my experience it’s not a release I’d be rushing out.

    I tried it tonight & found several web-related applications were un-usable and the browser itself was flakey. Toolbars would not stay put when locked, the IE toolbar (home etc) died, had to enable the menu to get to these functions.

    One good thing I did find, System Restore got rid of it and got me back to a working copy of IE6.

  257. MrBester says:

    "My approach was to write completely W3C compliant code, and see what happens"

    @Harry Richter: care to supply URLs? I for one would love to see a site whose code is fully compliant and valid and doesn’t render in FF as well as it does in IE6.

  258. Eruc says:

    Who seriously used IE at all anyway – pointless

  259. Great!  Get it out the door and into people’s hands.  In the meantime, what’s the rough schedule for the next release (7.1? 7.5? 8?) ?



  260. We should scrap IE all-together, if we recommend and get people to use better browsers (namely Firefox), it’ll help push the internet away from Microsoft. Also, it’ll solve the ever-persistant problems we developers have had with IE – standards compatability. Currently, I have to use <!– if[ie] //–> to get things done correctly; something I really shouldn’t have to do. IE in itself is a seperate web standard and really does not accomodate well with anyone.

  261. Mike says:

    IE 7 is still so full of major bugs that have gone unresolved (and in some cases simply ignored) that I find it extraordinarily poor judgment to force this release on the public.  The so-called blocking tool is a joke, since it doesn’t block anything.  For end-users, they will all of a sudden find they don’t know how to use their browser, are unable to fully surf the internet, unable to use many of their applications which require internet access, and can no longer request help from their tech friends once all this happens because RA no longer works.  All this for "security"?  IE 7 Beta 4 (this is not a release candidate) needs at least 2 more beta cycles to eliminate the major bugs, never mind the cosmetic issues.  

    Is anyone from Microsoft even listening?

  262. Tommy K says:

    Quote from Harry Richter:

    >>I am writing code for webpages as part of my job, mainly for one big customer. My approach was to write completely W3C compliant code, and see what happens. Well let’s see the outcome:

    IE6: displays as expected

    FF 1.0 to 1.5: rendering buggy, some things missing

    IE7: displays OK

    FF 2: with two small exception renders OK

    << End of Quote.

    One point in your statement makes me doubt it.

    Firefox 2 uses the same Version of the Gecko Rendering Engine that 1.5 does as Fx2 is a End-User Update.

    Besides, an example Website of yours would be appreciated.

    Well, I don’t doubt IE can show compilant pages as they should (mine does as well in Fx, Opera and IE7), as said the designers posibillities are just so limited in many ways (i.e. no generated content).

  263. kakudmi says:

    IE7 fails to open a popup javascript window if for example you have thumbnails of photos and you want a javascript window to pop-open if you want to see a large size of that image. Here’s an example:

    and try clicking on any of the images with IE7.

    Hopefully, MS developers will see this message and try to fix it. I tried using IE7 for 24 hours and quickly uninstalled it.

  264. se pe msn blogu. Doufm, e si to nikdo z mch nvtvnk nenainstaluje, protoe pokud ano, za nic nerum 🙂

  265. Dave P says:

    The fact that you are asking this question shows how woefully out of touch you are with web developers.

  266. I.T. Schlep says:

    Knowing my organization, we will probably use IE 7’s first year as the year for preparation and when IE 7 turns 1 year old, we will probably be ready to unleash it (officially) to the rest of the organization.

    Yah, it’s been a struggle but, I’ve long since gotten used to having end-users who know more about newer technology than us I.T. guys.

  267. Matt says:

    I can’t wait for IE 7.But what day will it be released? Because i forgot and i want to know again so i can let the rest of my site visitors know as well.

  268. EricLaw [MSFT] says:

    @Mike: The blocking tool blocks install of IE, which is exactly what it’s designed to do.  Are you having trouble using it?

    The issue with IE7 causing problems with launch remote assistance from the help and support center has been fixed.

    @kakudmi: Your page works just fine, Javascript popups and all.  They do open to the far left, due to the Left=10, top=10 directive in your optIE variable.

    @Matt: We haven’t announced the official release date, but it will be later this month.  Stay tuned to the blog for the latest news.

  269. Carlo says:

    IE7 fails to open a popup javascript window if for example you have thumbnails of photos and you want a javascript window to pop-open if you want to see a large size of that image. Here’s an example:

    This works for me… Do you have the popup blocker turned on?

  270. Saskia says:

    Why is IE 7.0 not compatible with Joomla? When I use wrappers in my site, you cann’t see them with IE 7.0

    I do hope they fix this before next week!!!

  271. Lord Titwillow says:

    Your description sounds marvellous! All it lacks is credibility.

  272. Bert says:

    No we’re not ready! IE7RC1 has got a major problem with javascript tooltips (domTT) we’re using in our application (see:

  273. David Kennedy says:

    Put yourselves in the shoes of CIOs and IT staff and stop being vague about release timing.


    IE 7 will be released on X Month, 2006.

    IE 7 will be pushed through Automatic/Microsoft/Windows Update on Y Month, 2006.

    We need to know when the final release date is and we need to know when you’re going to try to force feed it.  And those dates should be separated by 2 or 3 weeks at least.

    You’re setting yourselves up for some horrible press by not being clear when things are going to happen.

  274. Thogek says:

    Is this an accurate response to the last comment?

    "The final release of Internet Explorer 7 is targeted for release October 18th …and will be delivered to customers via Automatic Updates starting November 1st…"

  275. Gazza says:

    All this "should I upgrade?" decisions would be made much easier if the upgrade was mandatory, rather than optional. IE7 isn’t perfect, but if it could wipe IE6 from the majority of ‘net connected machines, web design would be much easier.

    Surely the hardware requirements for IE7 aren’t that greater than IE6?

  276. Frank Pilone says:

    I use IE 7 on occasion, and it is better than IE 6. It does have better support for CSS Positions which is used exclusively on two of my three editions. However, it requires installation of other software for things that would have been granted in 6.0 This is a security risk. Also, when opening a new window, it opens a new browser instead of a new tab. This defeats the purpose of using tabs. Because of these issues – I am sticking with Mozilla which I found to be better – even with the latest edit of IE 7. MS is on the right track with the software, but still has a way to go. I don’t like the idea of shoving the browser down the throat, but I am sure MS in all its wisdom knows better there – yeah right. As for IE 7 needing to be checked for site compatibility, it should be noted that most of the web sites there do not follow XHTML standards. Therefore, the blame falls partially on the designer there. If the page is written properly, IE should work mostly.

  277. Robwha says:

    So I read through the checklist of apps and toolkits I have to run through to make sure my EXISTING website will work with IE. I once again am reassured that Microsoft is blind to reality. We the consumers aren’t here for them. They’re here for us. Wake up, make a browser that works to standard, get it right and stick with it!!!

  278. Tino Zijdel says:

    Just to report that I had a nice e-mail conversation with EricLaw about some of IE’s HTTP-related quirks. It seems that standards and recommendations are not always perfect and sometimes do need some polishing. MS is at some points ahead of the actual standards which causes incompatibilities with other vendors’ implementations. At some points though MS’ implementations are not always perfect either or even lagging behind because the current standards aren’t perfect yet.

    Also regarding f.i. CSS I am the last one to say that CSS2.1 is a perfect standard; it isn’t, but it lacks a good implementation by one of the market-leaders in browser-software. That fact alone causes a stand-still in development of the specification itself, and IE7 is prolonging this stand-still by the mere fact that it still does not have a complete and (more or less) bugfree implementation of CSS2.1. That is what I find troubling about IE7: it doesn’t help standards-compliance but contradicts it by still requiring hacks and workarounds for some things that are well defined by the specification.

  279. Arvind Patel says:

    I am currently running IE7 RC1. I have one small issue with the favorites centre. I have created a lot of folders in IE favorites and each folder is having 10 to 12 sites.

    When I click on any folder it automatically expands revealing the contents of the folder. When I click on any other folder it also expands while the previous folder is still not collapsed. Due to this the whole favorite area becomes very messy when 3-4 folders have been clicked and it makes navigation very difficult and one has to navigate through the scroll bar on the right.

    I would suggest that whenever a new folder is clicked all previous folders should collapse automatically so that the navigation in the favorites area is easy and smooth.

  280. Microsoft – Heal thyself!

    Using IE7 RC1 at MSNBC, none of the videos work. I guess they aren’t ready yet. When I asked them about that, they said they were working on it. ;(


  281. stevenmc says:

    Dear Microsoft.

    Save time. Save money. Improve customer and developer satisfaction.  Become the best.

    Ditch Trident – Use Gecko.

    Nobody will think less of you.  Then you can concentrate on the browser implementation details that will really make your product stand out!

  282. stevenmc says:

    IE8: Ditch Trident – Use Gecko.

    Then you can concentrate on browser security and all other great implementations rather than bothering both developers, and those for whom they develop, i.e. your customers, Microsoft!

  283. gostaria de receber mais informaçãoes sobre ie7

  284. TMaster says:

    This makes me wonder. IE previews have required me to validate my Windows installation. But IE7 is also a critical update. And AFAIK, Microsoft has said critical updates do not require users to pass validation.

    I guess that’s good news – by releasing it as a critical update and not requiring users to actually pass the validation, web developers won’t have to cope with IE6 for too long.

    I’m glad Microsoft is doing what they can to update IE6 on ALL computers – and not just the ones that pass WGA validation, that would’ve been a real bad decision for the entire world. It would’ve shown how Microsoft does not care one bit about web developers at all, as well.

  285. TechBlog says:

    By JIM THOMPSON Buried deep in this press release from Microsoft (see the third paragraph under section "Getting Consumers Ready for Windows Vista Now") is news that Windows Media Player will release on October 24th and that Internet Explorer 7…

  286. ErnieDV says:

    I’d love to download the IE7 Readiness Toolkit.  Unfortunately, MS has once again shot itself in the head by requiring the installation of Windows Genuine Advantage so that you can download the toolkit.

    I use Firefox. Period.  IE is used only on those rare occasions when I encounter a brain-dead site that is IE specific and I can’t live without, or for testing new web stuff.  I DO NOT DO WGA.

    Now if someone could point me to a non-protected mirror it would be nice.

  287. For those who have seen some of my prior posts, you know I’ve been harping on why I think RSS (really simple syndication) is great. Last Friday, Microsoft’s Internet Explorer version 7 (IE7) blog confirmed that we will all be…

  288. sammy says:

    the text is copy of the hompage have……..

    The final release of Internet Explorer 7 is targeted for release October 18th …and will be delivered to customers via Automatic Updates starting November 1st, a few weeks after it’s available for download. Are your Web sites, extensions, and applications ready? Microsoft recommends that Web sites and applications be reviewed and made ready for the release of Internet Explorer 7 this month.”

  289. I think We must all realize that Microsoft won’t give a heck about things We have been knowing, reporting and telling for years about the really impressived poor performance of it’s Internet navigator, so I suggest with keep focused on intelligent and important questions about how to deal with IE, specially the new creature 7.

    Therefore here is my first question: Is there a posibility of separate conditional IE6 CSS programming from IE7 conditional CSS instructions, specifically throught conditional properties given with tags <!–[if IE]> in HEAD section of the html document?

    Please forgive me if this is not new, but I really need to know it so badly.

    "IE7 Is Coming This Month…Are you Ready?"…come on, you guys are really funny. Thank you so much in advanced for any help you can provide.

  290. Brian H. says:

    Internet Explorer 7: The Revenge


    How to make our jobs twice as irritating as they need to be.

  291. zooplah says:

    @ieblog: I wonder.  Is it scheduled for our October or Microsoft’s October (December)? 😉

    @goose: The problem isn’t about whom creates the standards.  It’s that IE is tragically behind the competition.  If MS wants to create their own ways of doing things, let them and let the market decide which to use.  But with their need to quickly catch up, I doubt they’d want to waste their time when the standards are already viable.

    @Aedrin:  I certainly hope you’re kidding.

  292. matt says:

    LOL at the incompetent IE "developers". Go back to school, learn how to program, and then get back to internet browsers. Please. I find it amazing that groups like Mozilla and Opera can create better programs than what Microsoft creates.

  293. pcdinh says:

    It is really good for IE’s development team if they use (X)HTML, CSS, Javascript engine from Mozilla Firefox instead of very buggy IE 6/7 engine.

    Someone here can download Firefox at, surf to some Ajax and CSS-based site and see the difference.

    Mozilla Firefox now is far better then Internet Explorer

  294. It seems that Microsoft has announced their plans to push out their new iteration of Windows Internet

  295. Chris says:

    Will it also be released for x64 this month ?

    I am glad it will be shipped i mean it ain’t perfect but it’s allot better then IE 6 for webdeveloping 🙂

  296. EricLaw [MSFT] says:

    @Chris: 64 bit versions will go live at the same time as the 32 bit versions.

  297. Anton Kunckle says:

    I’m using RC1, and like it. But there’s one BIG reason that I cannot use this as my primary browser. Without an equivalent to Firefox’s login  site id and password feature, IE7 remains a poor 2nd cousin. My current ID and Password list in Firefox must be 50-100 entries long.


  298. Michael says:

    For a group touting how wonderfully standards-based IE 7, you should really get talkin’ with the web developers at your own company. The website for Vista loads beautifully, but the rollover feature of the menu on the left is broken. I hover over any one of the graphics and the whole button disappears. Not good. Get this fixed if you actually consider RC1 a "candidate" for release. Because it’s far from perfect.

  299. I will be removing Windows XP professional & move to linux

  300. Kelly White says:

    Many of you already know this, but I&#39;m going to mention it anyways. From the IE7 Blog The final release

  301. Here are my weekly notes: My Dad was in town for the weekend – it was good to see him. It was probably…

  302. Name says:

    simple Chinese version,waiting,quickly.

  303. IE7 will be released this month – as in the next couple of weeks! Internet Explorer 7 brings the browser

  304. I have been using IE7 since the first Beta, and have not have any problems with my site or any of the other 6 web sites I maintain.

    Nor have I had any problems with any other web sites that I usually visit, and I am using IE7 at work and at home (using WinXP Pro, WinXP Home and WinVista), which means I am usually using it for about 18 hours a day, 6 days a week!!!

    Think IE7 is their best version.  Really glad they have listened to the users and added tabs… great time saver.

    New anti-phishing and secure certificate facilities are great and will help so many web/pc users against fraud.

    Well done MS.  Great job.

  305. Adam says:

    I’ve been ready since you first announce that IE7 will be available for XP SP2. This is better than IE 6 so i have no complaints. Thanks IE Team, hope to see this browser this week crossing my fingers.

  306. Teltel says:

    Are you ready? The final release of IE7 is fast approaching … and I mean really fast … No need to update anything in your compute.. or any Application Compatibility Toolkit tests. Just install and stay safe 😉

  307. Johann says:


    "This page you’re reading now is "invalid XHTML" (a phrase that deceives in implying that invalid XHTML is still XHTML, rather than tag soup) in no less than 77 different ways"

    When I clicked the link and attempted validation, it showed 215 errors – the last being a missing &gt;. Tag soup is correct.

  308. Mike Dimmick says:

    @Arvind: that’s an option. Tools, Internet Options, Advanced, Browsing, Close Unused Folders in History and Favorites. Check it, click OK, then restart the browser.

  309. M. Clover says:

    Been using RC1 and pleased that the corporate website I’ve been developing (3-col. CSS layout) doesn’t break. Woo hoo. There is a Santa Claus.

    Took a long time to drink the Kool-Aid but no longer scared of MSFT browser updates. This one may be the gipper.

  310. slslslslslslsls says:

    I think IE7 still has a few to many kinks to be released right now (unless Microsoft releases updates to the bugs via Windows Update)

  311. steve says:

    IE7 still does not recognize a height of 100% inside a tables TD. Try this example in FF and IE to see the difference:

    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" ""&gt;

    <html xmlns="; xml:lang="en" lang="en" style="height:100%;width:100%">

    <body style="height:100%;width:100%">

    <table border="1" style="height:90%;width:90%;">






    <table style="height:100%;width:100%;border:1px solid red">


    <td style="vertical-align:top;text-align:left;">



    <td style="vertical-align:top;text-align:right;">





    <td style="vertical-align:bottom;text-align:left;">



    <td style="vertical-align:bottom;text-align:right;">










  312. VaticNZ says:

    One thing I never understood: If all these companies are supposedly on-board with CSS compliance and what-not, why is there not *ONE* jointly developed, royalty-free rendering engine from W3C, for example?

    Do what you like with the interface and any proprietary functionality, but the base rendering engine is the same regardless of vendor/browser/platform.

    Wouldn’t it make life so much easier for so many?

    Ahhh… utopia.


  313. Keith Knutsson says:

    So many insightful bloggers and comments. Thank you to all for sharing your wonderful insight.


    Keith Knutsson

  314. SAF says:


    I have been using IE7 for some time and it used to work fine. But lately whenever I try to launch it, it *always* crashes.

    I have also tried launching it with no tabs and also with no add-ons, but no luck.

    Can someone PLEASE HELP.

  315. Mike says:

    The blocking tool moves IE7 from ‘critical update’ to ‘recommended update’. What’s needed is a tool that makes it impossible for people to install IE7 because it is simply one of the buggiest pieces of software I’ve seen in a long time.  Or – better yet – someone at Microsoft needs to realize forcing this out is going to be a huge mess.  

    As for Remote Assistance (and the help & support center in general, and other programs requiring internet access) not working, there are five bug reports on this all but one of which have been closed as solved.  Given that RC1 still had this bug and there is not going to be an RC2, I’m not convinced this (along with the numerous other unresolved bugs in RC1) has been fixed.

    IE7 appears to be trying to do too much too soon.  Will 7.1 be any better?  Only if Microsoft gets it to work, rather than trying to add more ‘stuff’ to it.


    @Mike: The blocking tool blocks install of IE, which is exactly what it’s designed to do.  Are you having trouble using it?

    The issue with IE7 causing problems with launch remote assistance from the help and support center has been fixed.

  316. Max says:

    today : 10/19/2006 05:21 (GMT +7)

    i saw IE7 released on :

    but when I check on Microsft website and this blogs, there’s no single link to official link to IE7 full version at Microsoft Download website.

    please announce this to everyone

    sorry if I wrong post

  317. C.B. says:

    The auto updates push certainly makes more work for M$ customers. Since we don’t yet have SMS in-place and implementation of domain managed restrictions on this update are iffy, our network and IT staff will be busy when this update is released.

    At least IE 7 appears to work properly with OWA so we won’t be completely up the creek.

  318. Alien says:

    It’s not fake, that’s for sure. Take a look at official IE7 page (MS):

  319. J.D.Robert says:

    I am

    – using genuine windows with SP2

    – using IE7, update beta 3

    and for quite some time now it works fine for me. I also intend to test it also on some picked company PC’s.

    Hope it will also work fine.

  320. Mark says:

    Yes its available, running it now,

    only crashed once and i’ve been running for a couple of hours (i’m a web developer)

  321. Nick says:

    Let the vulnerability announcements begin!

  322. Kevin says:

    The automatic update of IE7 locks up when it

    gets to "Checking for required updates", It just sat there for an hour or so, I had to kill it off.

    I had IE7 RC1 and the install put IE6 back on it.

    I tried to update IE by downloading and performing the install only to get the same results.

  323. Matt Miller says:

    I just bit the bullet and installed RC1 on my primary machine…..btw is rc1 the most current?

    anyway….the toolbars won’t lock into the custom positon I assigned them, but rather go back to their ‘defualt’ position when I click ‘Lock Toolbars’    grrrrrrrrrr

  324. User says:

    How do you install it on a machine that has no internet connection?  I want to upgrade my stand-alone machine to the neater interface.  (IE is used to develop other stuff and not just websites before anyone asks!)

  325. Le blog d’IE a annoncé vendredi dernier que Internet Explorer 7, version finale, serait disponible ce

  326. IEBlog says:

    Just in case you missed it somehow, we released IE7 last Wednesday . In the first four days over three

  327. I’ve had a number of people ask me about Internet Explorer 7, which was released last week . It is currently

  328. According to Microsoft’s IEBlog, IE7 is coming this month…Are you Ready?, with auto-update kicking in a few weeks after the download is made available. Most of the expected compatibility issues are in CSS filter hacks that will no longer work…

  329. Wenn man dem Blog-Eintrag von Scott Graff glauben darf, dann kriegen wir den IE7 noch diesen Monat. Dieser

Skip to main content