New Outlook Won't Use IE To Render HTML
loconet writes to tell us about a little surprise coming in Outlook 2007: it will render HTML email using the MS Word engine, dropping the use of IE for this purpose. This represents a body-check to the movement towards Web standards. Whatever you think about HTML email, lots of it gets generated, and those generating it won't be able to use CSS any more, and may stop pushing for more widespread standards support. The announcement was made on MSDN. From the Campaign Monitor post: "Imagine for a second that the new version of IE7 killed off the majority of CSS support and only allowed table based layouts. The web design world would be up in arms! Well, that's exactly what the new version of Outlook does to email designers."
But why should the job title "e-mail designer" even exist? Why does e-mail even need design? The point is to get in, communicate, and get out. Making the presentation of this communication unusually attractive is for PDFs and for advertisements.
It has ALWAYS used Word to render the HTML.
And if it DID change from this to IE, the geeks would be complaining the same -- because IE is a lot more tied to the system than Word.
Beyond this, the items that don't get rendered are good things -- for *EMAIL*.
I don't want someone being able to play with images too much. I don't want messages sent to me fucking with the positions. I don't want Javascript running in my email. I don't want forms that could potentially read the rest of my inbox available (if the JS were activated that geeks are getting up in arms about).
Almost everything that Word doesn't do are features I don't want my email reader to do.
Then again, I read my mail in plain text. I don't use Windows, I'm on a Mac right now using Foxfire (I don't like safari). My business lives off of BSD and Linux for our servers. And fucking shit...I'm having to defend Microsoft on this.
Now Microsoft will have TWO HTML renderers to debug and maintain. They had enough trouble with one.
Now we'll see exploits for IE and exploits for Outlook's renderer.
They've made the rendering part of the OS. If you cannot replace it with a different one, at least all of their apps should rely upon the same, built-in, OS functionality.
A single 500KB message is not a problem.
I have over 10,000 messages in my mail box. Now you can see the problem? And I'm just one person. On a network, this can quickly become a major issue.
Think of the problem with 1,000 employees, with 5,000-10,000 messages each at a company.
Not to mention that spammers love this because they can get this past the spam filters very easily.
I think it is time for us old farts to give up this fight, and admit we lost--and that we lost because we were actually on the wrong side.
Consider regular mail. The kind you put on paper and send in an envelope via the post office. If I were sending someone a regular mail asking them, say, about a strange spike in bandwidth usage last Tuesday, I would, naturally, include a graph showing bandwidth usage for the week. And if I also mentioned that the new server rack was in place, I might include a photo, either separately in the envelope, or inline in the letter.
Now let's imagine email had never been invented, and we just came up with the idea. How would we design an email system? I think we'd think it obvious that we have to make it at least as capable as regular mail, and would probably come up with an HTML body plus attachments as the format (for portability, as opposed to word processor formats). I think there is zero chance we'd say "wait a minute...we'd better make this plain text only, because 25 years ago, many computers did not have graphical displays".