Desmond File

Blog archive

Microsoft Banishes IE HTML Renderer from Outlook

I was shocked to learn that Microsoft has torn the IE rendering engine out of the Outlook 2007 e-mail client. Going forward, HTML e-mails will be rendered using the rendering engine in Microsoft Word.

The move could have security implications, since it takes the well-targeted IE browser out of the loop. But Microsoft says the move is really an effort to unify the display and creation of rich e-mail content. Until now, Outlook has displayed HTML e-mail using the IE renderer, but rich format e-mails were created using the Word rendering engine.

Says a Microsoft spokesperson: "While IE7 is great, it was never intended to be an editing tool. That's why we made the decision to use Word's new HTML rendering engine for both reading and authoring content, which had been improved based on HTML and CSS standards. This allowed us to unify the rendering and editing engines together, rather than forcing customers using Outlook to use two different rendering engines (one for rendering HTML, the other for editing)."

Of course, a lot of businesses are unhappy about losing functionality.
The Word engine doesn't recognize Cascading Style Sheets, and display features like page background are unrecognized. That means more work for e-mail designers and Web developers, who may need to dumb their layouts down so everything looks consistent across Outlook 2007, older versions of Outlook, as well as various browsers.

I want to hear your thoughts on this one! Do you think Microsoft is making a mistake by pulling the IE rendering engine? Do you think this is a sign that Redmond is really putting security first? Or maybe it's a sign that e-mail should be plain text, and plain text only. Speak up and we may feature your answers in our next issue. E-mail me at mdesmond@reddevnews.com.

Posted by Michael Desmond on 01/17/2007 at 1:15 PM


comments powered by Disqus

Featured

  • How to Create a Machine Learning Decision Tree Classifier Using C#

    After earlier explaining how to compute disorder and split data in his exploration of machine learning decision tree classifiers, resident data scientist Dr. James McCaffrey of Microsoft Research now shows how to use the splitting and disorder code to create a working decision tree classifier.

  • Microsoft: Move from Traditional ASP.NET to 'Core' Requires 'Heavy Lifting'

    There are plenty of reasons to move traditional ASP.NET web apps -- part of the old .NET Framework -- to the new cross-platform direction, ASP.NET Core, but beware it will require some "heavy lifting," Microsoft says.

  • Purple Blue Nebula Graphic

    How to Compute Disorder for Machine Learning Decision Trees Using C#

    Using a decision tree classifier from a machine learning library is often awkward because it usually must be customized and library decision trees have many complex supporting functions, says resident data scientist Dr. James McCaffrey, so when he needs a decision tree classifier, he always creates one from scratch. Here's how.

  • Blazor's Future: gRPC Is Key

    Blazor guru Steve Sanderson detailed what Microsoft is thinking about the future of the revolutionary project that enables .NET-based web development using C# instead of JavaScript, explaining how gRPC is key, along with a new way of testing and a scheme for installable desktop apps.

  • Don't Do It All Yourself: Exploiting gRPC Well Known Types in .NET Core

    If you're creating business services that send dates and decimal data then you may be concerned that gRPC services don't support the relevant data types. Don't Panic! There are solutions. Here's how to use them.

.NET Insight

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.

Upcoming Events