{"id":1767,"date":"2015-06-11T18:29:25","date_gmt":"2015-06-11T18:29:25","guid":{"rendered":"http:\/\/freshinbox.com\/blog\/?p=1767"},"modified":"2015-06-11T19:03:54","modified_gmt":"2015-06-11T19:03:54","slug":"the-outlook-team-reaches-out","status":"publish","type":"post","link":"https:\/\/freshinbox.com\/blog\/the-outlook-team-reaches-out\/","title":{"rendered":"The Outlook Team Reaches Out"},"content":{"rendered":"

\"outlook-banner\"
<\/p>\n

I was contacted by Julia Foran a Program Manager on the Desktop Outlook team for some background on Outlook’s rendering issues.<\/p>\n

It must have been the Microsoft, It’s Time to Address Outlook’s Proprietary Email Format<\/a> article or the needling over Twitter that got them to take notice :)<\/p>\n

Is Microsoft FINALLY taking the needs of email developers and designers seriously? I didn’t want to get my hopes up as we’ve had promises from Microsoft to “think about”<\/a> Outlook rendering issues during the fixoutlook.org<\/a> movement back in 2009 that didn’t bear any fruit.<\/p>\n

However, unlike the past, Julia reached out with questions!<\/p>\n

Could you share some research you have demonstrating the impact to users, particularly ones reported by users themselves? Additionally, do you have a list of HTML tags that are commonly used but not supported in Outlook, or other specific rendering issues beyond just HTML?<\/p><\/blockquote>\n


<\/p>\n

How Shall We Approach This?<\/h4>\n

My initial reaction of course is to reply… “Just render emails in a browser already – like Outlook for Mac, Outlook 2003 and Outlook for iOS!<\/em>“. However that wouldn’t be… nice, would it? :)<\/p>\n

In the hopes of kicking off a cordial and hopefully long lasting dialog between the email community and the Outlook team, I’d like to get back to them with what they asked for.<\/p>\n