Any news about Outlooks rendering engine yet? I hope the integration of Office 365 made them adopt webkit vs Word.
However it's to Microsoft's benefit to keep their file formats rendering in obscure ways, as it makes it difficult for competitors to edit them.
The reason why Office made the switch to using Word as the default (and not even allowing Trident as an option) was to unify the layout results between authoring and reading emails. A common complaint "back in the day" was that users would write emails and they would end up looking different, since IE and Word render things differently.
While Word will read and render HTML, making it a standards-compliant rendering engine was and is not a priority (HTML is a convenient storage format that happens to also be rendered by other programs). So, the decision was made to make Word the default email renderer, and cut Trident from Outlook as an email renderer.
(I work on Word, but I don't and have never directly worked on wordmail, but I've heard this explained in hallways over the past few years when I complain that Word doesn't render animated gifs, I am not an official MS representative, etc. etc. etc.).
The flip side of the coin is fixing HTML rendering in Word such that we can pass Acid tests, but considering the sort of mail people send, what sort of tasks Word is used for, and the fact that a working renderer is a mouse-click away, and you can see that it's just not cost-effective to take on this work.
I guess the third side of that coin is to take out Word and use something else as an email composer, but that would break all sorts of things I can't even begin to think about and is even harder than making Word a great HTML renderer (which I think is completely doable, but again, not ultimately worth it).
I'm also not on the Outlook team, so they likely have a different perspective than I on this topic, but that's how I see things.
Word being added to the mix in the first place only reinforces that.