Update This study has since been superseded. View the latest edition
It’s been just over 12 months since I posted our original Guide to CSS Support in Email and quite a bit has changed since. Sadly, the most significant of these changes was in the wrong direction, with Microsoft’s recent decision to use the Word rendering engine instead of Internet Explorer in Outlook 2007. We’ve written plenty about it already including an explanation of the reasoning behind it. More on its impact on CSS support later.
It hasn’t all been doom and gloom though, a number of vendors have maintained or improved their support for CSS, especially in the web-based email environment. The new Yahoo! Mail looks very promising and the old Hotmail will be making way for the new Windows Live Mail in the coming months. Desktop based apps tend to move a little slower and not a great deal has changed on that front, but traditionally they’ve been the best performers anyway. This year we added Outlook 2007, the new Yahoo! Mail and Mozilla Thunderbird for the Mac to our test suite, and also noticed some subtle changes in others.
So what’s changed?
No doubt the Outlook 2007 “incident” had the biggest impact on CSS support in email over the last year. Many commentators in the industry claimed the change was no big deal, that this change doesn’t really make a difference. Funnily enough, most of these comments came from the marketing side of the fence, not the design side. Understandably, most marketers and project managers couldn’t care less about this change – there are ways around it using tables and inline CSS, so who cares? Well, designers care.
I wasn’t kidding when I said Microsoft took email design back 5 years. Using tables for layout is a dying art in the web design community, in fact many designers who have started CSS/XHTML in the last few years have never even coded a table based layout before. This is a good thing. CSS based emails are more lightweight, much more accessible to those with disabilities and because content is separated from presentation, much easier to dumb down for those reading email on mobile devices. This change by Microsoft means that for at least the next 5 years any designer not familiar with table based layouts will need to learn a completely different way of creating a HTML page if they want to send emails to an Outlook user.
The new Yahoo! Mail
On a much more positive note, Yahoo! have been putting the finishing touches on their brand new mail interface. Mark did some solid testing on the new Yahoo! Mail vs Windows Live Mail back in January, which is certainly worth a read. The exciting news is that Yahoo! have maintained their lead as the best web-based email client out there for CSS support. There are some subtle differences to the older version, which we’ve noted in our results below.
Early talk from the Yahoo! camp suggests they will not be forcing all of their current users to the new platform, but instead make it the default for new customers and give existing customers the option to upgrade.
Windows Live Mail
It should also be noted that Windows Live Mail (the new Hotmail), which we covered an early beta of in last year’s test is rolling out in the coming months. Unlike Yahoo, Live Mail will be completely replacing the older Hotmail interface over the course of the next few months, meaning our days coding for Hotmail’s quirks will soon be over.
It’s not all rosy though. In the 12 months since I last tested the Live Mail beta, they’ve dropped support for a number of key selectors and properties. As detailed in the results, a number of key CSS selectors are no longer supported. The most significant of these is
e.className, which as many of you know means inline CSS will be the only way to get much of your formatting to work for Hotmail subscribers moving forward. Very frustrating.
When I initially wrote about the Outlook 2007 shock a few months back, I said:
If your email breaks in Notes or Eudora, it was often an acceptable casualty, but if it breaks in Outlook, you’re more than likely ostracizing too many recipients to justify your design approach.
Unfortunately I still think this is the case. If there’s a chance that a reasonable percentage of your recipients will be using Outlook 2007, then a completely CSS based email design just won’t cut it. If your layout is column based, you have no option but to use tables for the basic structure of your email. You’re also going to need to dumb down your CSS usage (see our results below for the nitty gritty on what does and doesn’t work).
Business to Business emails
I wasn’t able to track down any predictions on Office 2007 penetration in the business world. Considering it was only released a few months ago, you might have some time before the install base becomes significant. Either way though, you’re going to get caught eventually. Considering Outlook’s 75% domination over corporate email, you’ve got little choice but to bow down and stick to tables and basic CSS for all your email templates.
The verdict: Table-based and possibly inline CSS.
Business to Consumer emails
Across the spectrum of consumer based email environments little has changed really. Yahoo! has maintained their position as the industry leader, while Hotmail has simply been replaced with new wrapping but next to no improvements. Just like last year, Gmail still provides very limited CSS support. If you’ve got a decent percentage of Gmail subscribers, it’s table based with inline CSS all the way I’m afraid. Of course, you can never assume that none of your home based subscribers are using Outlook 2007, so this is a judgement call you’ll need to make yourself.
If you do decide to stick with CSS based layouts for B2C emails, I’d recommend doing plenty of testing across Hotmail, Yahoo!, AOL and Gmail to make sure it’s presentable in each.
The verdict: Either CSS or table-based layouts but make sure you test, test, test.