Internet Explorer at TechEd 2007

The information published in this post is now out-of-date.

—IEBlog Editor, 20 August 2012

Many of you will be attending TechEd 2007 this year, so I wanted to summarize our presence at the Event.

As you know, TechEd is focused on current technology, so our sessions are focusing on unlocking the power of IE7. There are 6 breakout and 7 chalk talk sessions that you can visit to get in-depth information on Internet Explorer – and have the opportunity to interact with the members of the team. We’re also excited to have Molly Holzschlag doing a couple of sessions on Monday. If you have more questions, feel free to swing by one of the IE7 booths – there is one in the developer and one in the security area of the Microsoft pavilion.

Hope to see you all at TechEd!

Markellos Diorinos
Product Manager
Internet Explorer

P.S. Here’s a list of all the IE sessions

Breakout sessions:

CLI223 - Microsoft Internet Explorer 7.0 for the Enterprise (200)
Wednesday, June 6 10:15 AM - 11:30 AM, S310 A, Speaker(s): Mike Chan

This is an overview session on why you should deploy Internet Explorer 7 in the enterprise. We provide high-level coverage of features, IE7 as a developer platform, and finish up with a discussion about management and deployment techniques. Troubleshooting and application compatibility are also covered.

CLI229 - Building Trust with Microsoft Internet Explorer 7 (IE7) and Extended Validation SSL: Boosting User Confidence in Online Transactions (200)
Thursday, June 7 1:00 PM - 2:15 PM, N210 B, Speaker(s): Markellos Diorinos, Troy Kitch (VeriSign)

Improving the trust models for commerce sites is critical to help prevent consumer erosion of trust in online transactions from malicious Web sites and phishing attacks. This session discusses how Internet Explorer 7's support of Extended Validation (EV) SSL Certificates, designed to promote strong identification for Web sites, allows users to easily identify the real identity of the Web site they are transacting with and thereby helps boost their confidence in online transactions. Web site owners will find out how they can implement EV SSL for their site and best practices in implementing SSL-protected Web sites.

SEC305 - Microsoft Internet Explorer 7 (IE7) Security In-Depth (300)
Wednesday, June 6 3:45 PM - 5:00 PM, S310 E, Speaker(s): Markellos Diorinos

This session is an in-depth discussion of IE7 security features (Protected Mode, ActiveX Opt-In, etc.) and real-life experiences from Web developers in the past eight months with IE7. Best practices are discussed, as well as dos and dont’s for creating Web sites. Finally, initial plans for security features in the next version of IE are discussed.

WEB321 - Microsoft Internet Explorer 7 and the Route to Standards: Where Did We Start, and Where Are We Now? (300)
Monday, June 4 10:30 AM - 11:45 AM, N210 B, Speaker(s): Douglas Stamper

Internet Explorer 7 has fixed many of the rendering and other issues that caused headaches for Web developers and Web designers. We take a look at what caused Microsoft to bring IE back, where we started from, how far we got, and how our user base of over half a billion people affects the way we went about our work on IE7. Learn about where the platform started, why we didn’t take every fix you wanted, and what features we did add. Also, find out what we’ve learned since shipping IE7, and how that might affect future versions of Internet Explorer.

WEB322 - JavaScript Performance in Microsoft Internet Explorer 7: Making Your Web Applications Scream (300
Wednesday, June 6 3:45 PM - 5:00 PM, S320 E, Speaker(s): Cyra Richardson

What are the top five things that cause your code to run slowly in the browser? With the right optimizations, JavaScript can run quickly and efficiently in the browser environment. In this session, learn from the experts how you can make your AJAX/JavaScript applications scream. We look at the top five coding issues that cause JavaScript to run slow, how you can avoid memory leaks, ensure your don’t leave variables hanging around, and how you can avoid client side scripting errors.

WEB323 - The RSS Platform in Microsoft Internet Explorer: Pushing Out Rich Data to Your Users (300)
Monday, June 4 1:15 PM - 2:30 PM, N220 F, Speaker(s): Eric Lawrence

Internet Explorer 7 provides a rich RSS platform that you can use to push rich data out to your users. Many sites offer RSS feeds with simple text to their users, but most end users don’t know what that glowing orange button does, and fewer realize how they can use it pull down their favorite Podcasts, VidCasts, and other rich media. Learn how to add RSS to your Web site, create simple list extensions that enrich the data you push out, how to push include rich media in your feed, drive traffic to your site, get your user hooked to your content, and how you can create client side applications that use the built in platform.

Chalk Talks:

CLI01-TLC - Deploying Internet Explorer 7 in a Business Environment (200)
Thursday, June 7 9:45 AM - 11:00 AM, Yellow Theater 3, Speaker(s): Mike Chan

Come and discuss the value of IE7 to your business and talk about methods of distribution, customization, and how the IEAK can be used to meet your needs. Management topics and business feature requests for the next version of IE will be taken.

SEC03-TLC - Internet Explorer 7 (IE7) Security Hands-on: Extended Validation SSL and Phishing Filter (300)
Wednesday, June 6 5:30 PM - 6:45 PM, Yellow Theater 2, Speaker(s): Markellos Diorinos, Eric Lawrence

You’ve heard about IE7’s EV SSL support and the Phishing Filter before. If you still have questions about how exactly they work (and want to look at the root certificate store, validation chains, network captures), join us for this in-depth session.

WEB02-TLC - Microsoft Internet Explorer: Interactive (200)
Thursday, June 7 9:45 AM - 11:00 AM, Blue Theater 14, Speaker(s): Cyra Richardson

Come join members of the IE team and give them a piece of your mind. What do you want to see the IE team fix, what are your most common headaches, what can we do to make your lives as Web developers easier. This is your opportunity to talk with the IE team and help shape the future of the next version of IE.

WEB03-TLC – Web Blunders: The Top 5 Biggest Mistakes On The Web (300)
Thursday, June 7 4:30 PM – 5:45 PM, Blue Theater 14, Speaker(s): Pete LePage

Using the Web is a great way to share ideas, designs, HTML, CSS, JavaScript and other code. But it’s also a great way to share bad code! We show you the top 5 biggest Web blunders that cause problems for developers and end-users on the Web. Learn about the problem and how to fix it, and more importantly, how to avoid it!

WEB07-TLC – Web Standards Critique (200)
Monday, June 4 3:00 PM - 4:15 PM, Blue Theater 14, Speaker(s): Molly Holzschlag

Join Molly Holzschlag and her panel of Web experts to look at your sites and offer praise and suggestions on your HTML/CSS Web site. We’ll be as brutal or as gentle as you want, but come prepared to see some of the greatest (and worst) Web sites – yours!

WEB08-TLC - Web Development Tools for Microsoft Internet Explorer (300)
Thursday, June 7 2:45 PM - 4:00 PM, Blue Theater 14, Speaker(s): John Hrvatin

If you’re doing Web development, there are a number of tools available that work with Internet Explorer that can help to make your life easier. We look at some of the Microsoft tools like script debugging in VWD, the IE Developer Toolbar, Fiddler, and then some of the non-Microsoft tools like IE Watch, IE7Pro and some of the other great tools that are available. You’ll walk out of the session knowing new ways to make your development debugging easier.

WEB10-TLC – The Benefits of CSS and Web Standards Based Development (300)
Monday, June 4 1:15 PM - 2:30 PM, Blue Theater 14, Speaker(s): Molly Holzschlag

By now, most Web developers and designers are aware that Web standards are a critical industry concern. However, many people aren’t clear of the true benefits of working with a standards-based methodology. In this session, Molly E. Holzschlag, a Web standards and interoperability consultant for Microsoft, takes a look at the true benefits of Web standards. Learn how semantic markup, CSS, and intelligent script management can improve the appearance, performance, speed, accessibility, and search optimization of any site, save you money, and help you manage sites for the short and long-term.

Comments (22)

  1. Tom says:

    IE7 not a technology product but a marketing product. If IE7 make everything perfect, Microsoft will offend many cooperators and kill many developers passion. What IE7 should do is just like Firefox, make non-Microsoft development more easy and more fun. As tools mentioned above: IE Watch (, IE7Pro( and others not mentioned such as IE Spell( I would think the ie7 strategy is right

  2. ulimarv says:

    Look forward to the follow up info from these sessions.

    Did MS realize how important a reliable, always available bug tracking system is to the life of IE.

    Did MS realize that developers are tired of working around bugs in IE, and are expecting fixes for the known issues that do not follow standards, especially if the fix can be made without breaking existing functionality.‘frameborder’, 0);

    Should work, period.  Fixing this will *NOT* break /any/ existing sites.

    (there are dozens and dozens of cases like this)

    Did MS learn from internal employee fallout about the importance of getting this right, and not resting on their lorels (sp?) with the status quo.  Chris Wilson had a lot of interest in fixing stuff within the IE teams focus.. did the shift within the company get a fire lit under the right people’s feet to get these things done?  Dave Massy.. was one of the few MS employees that publicly admitted that parts of IE6 were atrocious and got the ball rolling to fix them in IE7.. then IIRC, jumped ship, just when things looked like they might turn around for IE.  When the captain jumps ship, the passengers have to wonder why the captain gave up?.. was the Iceberg too big? Has IE’s core engine given all it can without being properly re-written from the ground up? The developers want to know if we are on the Titanic or not.

    Did MS realize that "empty" promises of "we are working on IE8, and IE9" would be seen as such if we were not informed of the new bug fixes and planned features ASAP?

    Did MS realize that taking the feedback site offline at the critical moment when it was most needed was like software suicide?  Ever wonder why people like, and in fact love developing for Firefox?

    All gripes aside…… we are looking forward to more info on tools to help develop in IE (god knows we need the help!).

    Oh, when IE7 came out in Nov./Dec.2006 the quote at the time, was timely, yearly releases could be expected.  Since we are half way to that next release, can we get a link to the alpha/betas?  Is there a set of expected changes we can peek at? Road Map anyone?

  3. Ron says:


    Links, or it didn’t happen.

  4. thacker says:


    Links were e-Mailed to VeriSign, IE, the hosting companies as indicated by Whois search, Phishtank, the primary targets of the Phish, et al.

    If absolute documentation is necessary, enough people know how to get a hold of me.

    Deal with it.

  5. jung says:

    when will you autoupdate IE7 in korea,china and japan?

    we want to autoupdate ie7 in korea,china and japan because of idn(international domain names)

    when, when, when  — – –

  6. Dear Microsoft people,

    Please spend 20 times more energy, typing hands, efforts, saliva, brain cells, human resources, technological resources, etc.. on fixing known, documented, testcased and reproducible bugs (and W3C spec. violations) in IE 7 (in particular when in standards compliance rendering mode: compatMode == "CSS1Compat") than on lecturing others about web standards.


    – visit Bruno Fassino’s

    and visit Ian "Hixie" Hickson

    extensive demos and testcases. Spend time and energy on these Fassino and Hickson webpages and fix your own bugs.

    Please spend 10 times more energy into upgrading your whole, entire and very own website

    – to pass validation markup

    – to pass CSS 2.1 validation

    – to use semantic markup

    – to meet basic accessibility guidelines

    – to create a clear separation of content from presentation aspects thanks to CSS implementation.

    Pretty much everyone else (,,,,, etc.) have done so or is doing a much better job or is achieving much better compliance results.

    Start complying with and supporting W3C web standards yourself before preaching/lecturing others about these W3C web standards. You can not better lecture about W3C web standards by first supporting these W3C web standards and by complying with these W3C web standards to begin with. There is no better promotion of W3C web standards than by adhering to these and by conforming to these for yourself, with yourself, thanks to yourself to begin with. Practice what you preach by supporting, complying and conforming what you lecture/preach about. Start with your website, your products, your softwares. Act in a coherent manner, with a consequent attitude, with consequent habits in the products you control, in the websites you own, etc..

    Best regards,

    Gérard Talbot

  7. Fduch says:

    Sweet talks are good.

    But what about making browser that works.

    I mean if browser’s asked to run it shoud run. Not hung 30% times.

    If browser’s asked to open the link it should open it, not crash.

    If browser’s asked to save image/webpage it should do it and not throw some cryptic error codes around.

    And to think that mhtml MIME formats of IE7 in XP and Vista are not fully compatible.

    I wonder whether IE team (excluding enging guys) understand it…

  8. Fduch says:

    They will never answer this question but I’ll still ask it 🙂

    Windows has feature called "Error Reporting"

    How many errors with "hungapp" code were received from IE6 vs. IE7 since thier releases?

    I think that IE7 had already surpassed IE6 even though it was released not long ago.

  9. Shayne says:


    Will you be announcing IE7 *FINALLY* implementing SVG? Because that’d surely rock. Please 🙁

  10. thacker says:


    Again, you have temerity to mention security. Again, Wilson stated at MIX that security in IE is the greatest focus.

    Again, IE fails in identifying the simplest of Phish content, sub-domains that contain dual TLDs. Again, submission to your “human” assets fails to identify blatant Phish content.

    The two most recent Phish attempts that I have received, both older than Seventy-two hours from the date of receipt:

    IE fails to identify both as does Opera even after submission to the respective Phishing services.  Mozilla identifies the latter.

    The only browser that consistently identifies Phish attempts One hundred percent of the time is, of all things, the AOL browser.

    This lastest Phish received Sunday, 26 May 07, 0712HRS EST, was immediately identified as a Phish site by the AOL browser ver 8.0.  Yeah guys, the non-security edition of AOL.

    All other major browsers failed to identify this attempt.

    The AOL browser is still based upon your Trident engine.  Which brings to mind, that was some temerity to name that piece of crap that carries the same name as a class of Naval submersible craft with superb service duty, history and honor.

    Sidebar:  Speaking of which, if the Trident engine were an aircraft engine would you bolt that damn thing onto any commercial aircraft of any size?  hasLayout becomes hasThrust. Of course, it becomes somewhat problematic during takeoffs, landing, wind shear diversions, anything less than autopilot, of when hasThrust is either true or false. Do the words, “Crash and burn” have any meaning? But, Wilson has stated that it is a good engine.

    Again, anything less than a One Hundred percent identification of Phish attacks is absolute failure.

    Dozens have been accumulated and documented, including, again, VeriSign’s utter stupidity in not relying upon the browser’s referrer in presenting pseudo credentials from silly brand extensions on a VeriSign Web site and its use on Chinese domain based Phish attempts.  And no, the underlying code of the site being referenced does not obfuscate the Referrer Header.

    It is more than enough of a statistical pool to draw conclusions based upon the reasonable man standard.

    A Word document that substantiates claims made will be available … end of the week … 01 June 2007 to you and to VeriSign.  But, hell, notice was sent weeks ago and the problem still persists.  That documentation will be included, also.

    Again, what is so complicated that, for example, the Anti-Phishing Working Group cannot serve as a repository for the URLs of all financial institutions? That the access to the repository be only accessible to its certified membership?  That browser manufacturers are members of the same?  That such data is incorporated into a heuristic that compares the authenticated URLs to a purported URL when it is entered into the browser?  What is so drastically wrong with all the organizations, that accumulate Phish data, of sharing that data with a centralized repository?

    For Christ sakes, this is sub-domain use with dual TLDs. It is not quantum physics analysis of a Black Hole.

    You can speak of the complexity of XSS attacks, referrer re-directs, whatever, but one thing seems to always appear somewhere in all the bullshit, — An obfuscated URL.

    Again, the final analysis when compared to security of that one user, all the way to that 500 millionth user, I could care less about standards, bug reporting systems, CSS 2.1, fragmentation of HTML, etc. If browsers cannot identify a simple probable Phish site and do it off the bat, what future is there in combating such things as malicious obfuscated JavaScript.

    You have an obligation to those 500 million users.  Microsoft, after all, forced that browser down their throats.  

    Maybe you enjoy looking like a jackass, but I resent it.  I resent all talk and no cattle. I have lost tolerance for people who lack the ability to do things right and who lack forethought and the ability to put their own self-serving interests aside.  I take safety and security very seriously.

    Do your job, get the basics done and do it right. If you can’t even do that, get the hell out of the business.

    The average guy deserves much better.

    Again, it is time for the entire Internet Communication chain to get their heads and asses wired together.  Enough is enough.

    As far as a formal thank you, or respect, from here on out, it has to be earned.  Until then, you will continue to be dealt with in the disdain that you have worked incredibly hard to earn.

  11. everyman says:

    Any idea why you don’t support MJPEG? Is it because IE, and its developers, are basically just stupid? This is a serious question, and I would appreciate a serious response.

  12. Steve says:

    "Any idea why you don’t support MJPEG? Is it because IE, and its developers, are basically just stupid? This is a serious question, and I would appreciate a serious response."

    Why should *IE* itself support M-JPEG? It’s a video format, and so should be supported via a plugin.

    IE doesn’t support MPEG, WMV, etc natively – so why should M-JPEG be any different?!

  13. fed-up says:

    MS have also invented an interesting lock-in technic to stop the developers that use IE7 engine.

    How? In beta 1 or 2 they implemented the keyboard layout bug that pissed all non-english users of IE7. After some months they "fixed" it via a hack in the browser code (or something similar). So developers of alternative browsers that use IE7 engine have to invent that hidden hack themselves or their browsers wouldn’t work.

  14. Ever annoyed says:

    Just once I’d like to read one of these things without some rabid firefox lover rambling on.

    Don’t get me wrong, I love CSS design.  It truly makes life easier and makes so much more sense.  Nothing else has really made an impact on css based designs, even though a fair few things have tried.  Flash web sites aren’t really websites if you ask me, they’re web hosted applications.  😛  No I don’t like flash web sites!

    Anyway, the point of my rant is simply this:  Regardless of what microsoft do or don’t do with IE and CSS, it is, by default, the /actual/ standard for web delivered content.  No matter how you read the stats, ie still has a significant majority.  I laugh everytime I hear web developers stating they don’t develop for IE.  Idiots.  Yes, not using hacks is good, but in the world where we build sites for paying customers who want their sites to work with the majority of browsers, you have to develop for IE first and its features, rather than having some pie in the sky alternate design that you’ll have to spend more of their money to work on IE.

    In short, if you’re a real designer living in the real world, quit your whining… Microsoft are still making you money.

    Life will get steadily easier, but quit wishing for firefox domination.  Time has pretty well shown, its not going to happen.

  15. Hexaae says:

    Unless IE won’t have a bugreport feature where users can send bugreports and help IE-team to notice and fix bugs quickly, FireFox will always be a step ahead in development.

  16. jacob says:


    You are partially correct.  We all make money/maintain employment because so many users out there are using IE as their default web browser (heck, most don’t even know there are other browsers out there!)

    But you’ve nailed the Catch22 issue here.  Since we *Have* to design for IE users, we *Have* to endure countless *infractions* of the specs out there, which cause us to lose hair at an alarming rate.

    In addition, advances in the "Web", in terms of XForms, CSS3, SVG, Canvas, etc. just can’t happen, because we have no idea if IE will ever support them, or when they will.

    The problem we have now, (that wasn’t so apparent before), is that these technologies exist now, and getting tons of exposure, since most other browsers support them, or are road mapping support in.

    No longer is IE the cream of the crop by default.. now IE is significantly behind, and trying its best to catch up.  Some think that "new features" (ie. RSS support) are the ticket to getting ahead, whereas the developers out there, are pretty darn sure that a respectable level of CSS & JavaScript support would be more than sufficient to keep IE in the game.

    Simply being able to call all DOM methods, as defined in the spec, and have them work, would be a godsend.  Having to know, that "oh, they all work, except… this, that, and those" is a royal pain.


  17. " I laugh everytime I hear web developers stating they don’t develop for IE.  Idiots. "

    I develop for Gecko and patch all other browsers accordingly. IE is actually the easiest browser to patch if you read the MSDN’s IE documentation. Using IECCSS I can also enjoy using MS’s proprietary stuff without breaking any standards.

    If you think IE sets standards just because it’s the majority browser then you’ve got a little research to do. It has it’s place; it’s difficult to design for by default unless you know about available resources. Using those resources IE does trump the KHTML rendering engine (3.5) as far as what it’s potentially capable of supporting and it can look pretty good. Opera 4 has the earliest (potential) quality rendering engine. I love research…

  18. Here is how to research what I have mentioned above…

    Test IE with and without patching…

    No Patch

    With IECCSS Patch…

    If you want to test the KHTML engine but don’t want to deal with Linux as your main OS run it in an emulator. Easy enough directions at…

    Lastly Opera 4 is available for download at…

  19. thacker says:

    Very interesting article from CRN — Published 29 May 07. Titled: Vista, XP Users Equally At Peril To Viruses, Exploits

    Some interesting notes regarding IE7.

  20. I am creating websites and learned CSS but I found out that IE7 does not support CSS like the other browsers such as Firefox. When is Microsoft going to fix that problem. Also, there is a significant difference in web viewing between IE7 and other browsers with IE7 being dramatically inferior. Is that going to change and if so when.

  21. IEBlog says:

    A while ago I talked about Internet Explorer sessions we were giving at Tech-Ed 2007 . And while it was

Skip to main content