I love my Gmail.

No kidding, I'm a Gmail slappy. It's simple and it works. Its spam filters are 99.9% right in my experience, and with spam making up as much as 80 percent of all email, you know that's a time-saver right there. Plus, I can check my Gmail anywhere I have access to a web browser, even on my little not-quite-a-smartphone Samsung SCH-u740. I don't even have to pay for a data plan. I recommend Gmail to everybody. Or I have been until now.

Gmail has one nagging problem which is threatening to drive a wedge between us. While Gmail is supportive of me in so many ways, it's lacking in its support of HTML and CSS standards. Not just a little; I'm talking hardly any support at all. So I never get the full experience of the lovingly crafted HTML emails that other clever web designers have created for me, just Gmail's limited interpretation of their intended appearance.

You might say, isn't that a good thing? After all, email should be all monospaced, with no graphics. Everything would run a lot faster that way. And I'd agree with you, if this was still 1990.

The main issue here is compliance with web standards. As a web designer, I know the frustration of having to create multiple versions of pages for specific browsers, because each one handled the interpretation of HTML a bit differently. While the major browsers have come a long way towards standardization (and Microsoft's about face regarding Internet Explorer 8 last month was another big step in that direction), both desktop and web-based email clients support web standards anywhere from completely to not-very-much-at-all. And Gmail falls into that second category.

It's not like it can't be done. Yahoo! Mail supports HTML/CSS standards very well, as tested by the Email Standards Project. So does Mozilla's desktop email client, Thunderbird. So why not Gmail?

Google, it's time to show the love back to your Gmail fans. Consider the recommendations from the Email Standards Project, and make Gmail compliant with web standards. Your users - and thousands of web designers - will thank you for it.

Email Standards Project - Gmail Grimaces from Mathew Patterson on Vimeo.

Hat tip to Amy Stephen of OpenSourceCommunity.org for the info about the Email Standards Project.

Many web developers breathed a sigh of relief yesterday, myself included, when Microsoft announced that the new version of Internet Explorer would adhere to current web standards by default. Originally, the idea was to make IE8 more backward-compatible, using IE7's "standards" mode by default, and forcing web programmers who wanted to use IE8's "standards" mode to specify that in a page's HTML code. With yesterday's decision, IE8 will default instead to its own "standards" mode.

Why is this important? Doesn't it mean a lot of work to update and add code to older web pages? Probably. All current browsers have two main rendering modes: "quirks" and "standards." When a browser is asked to load a web page that requests a current DOCTYPE in its code, the browser uses its own standards mode to render the page. Older or improperly-formed web pages, that either reference older standards or have no specific reference to a standard, are rendered using "quirks" mode, where the browser tries to emulate an older version in order to display the page.

The problem is standards change over time, as new technology creates needs for browsers to handle content they didn't need to before. Plus each browser has its own way of implementing "standards," so you can see the dilemma web developers are faced with when creating web pages.

When Microsoft released IE7 in October 2006, some web pages that had rendered correctly in IE6 looked bad in the new browser. This was due to changes in the "standards" mode between the two versions, which also exposed some workarounds developers had used during the five years IE6 was the dominant Windows-based browser to get it to render certain objects properly. One example was the incomplete support for alpha-channel transparency in PNG images in IE6 and earlier. Developers had to use code that determined which version of which browser the site visitor was using, and apply a workaround if IE6 or earlier was detected.

When three out of four computer users are viewing web pages in a browser made by Microsoft, whatever decision Microsoft makes carries a lot of weight. Microsoft's original decision to set IE7 "standards" by default, while understandable from a compatibility standpoint, would have crippled future development of web technology by tying standards to the older, IE7-era.

Dean Hachamovich, Microsoft's General Manager for Internet Explorer, summarized the company's decision this way:

"Long term, we believe this is the right thing for the web. Shorter term, leading up not just to IE8’s release but broader IE8 adoption, this choice creates a clear call to action to site developers to make sure their web content works well in IE."

It may mean some short-term pain for web developers who have to upgrade older pages, but Microsoft's announcement yesterday that IE8 will embrace current web standards by default, whether prompted by pending litigation or a newfound love of open standards, means the future development of the web will be looking forward instead of backward. In the long run, that's good for both users and web professionals.