Word 2007 HTML and CSS Rendering Capabilities in Outlook 2007 (Part 1 of 2)
Summary: Learn about support for the HTML and Cascading Style Sheets specification provided by Word 2007 and Outlook 2007. Word 2007 HTML and CSS Rendering Capabilities in Outlook 2007 (Part 2 of 2) provides instructions to install and use the Outlook 2007 Tool: HTML and CSS Validator. (24 printed pages)
Zeyad Rajabi, Microsoft Corporation
Erika Ehrli, Microsoft Corporation
August 2006
Applies to: 2007 Microsoft Office System, Microsoft Expression Web, Microsoft Office Word 2007, Microsoft Office Outlook 2007, Microsoft Office SharePoint Designer 2007, Microsoft Visual Studio 2005
Download Outlook 2007 Tool: HTML and CSS Validator.
Contents
-
Introduction to HTML Parsing and Rendering in Outlook 2007
-
Supported HTML Elements, Attributes, and Cascading Style Sheet Properties
-
Conclusion
-
Additional Resources
Introduction to HTML Parsing and Rendering in Outlook 2007
Microsoft Office Outlook 2007 uses the HTML parsing and rendering engine from Microsoft Office Word 2007 to display HTML message bodies. The same HTML and cascading style sheets (CSS) support available in Word 2007 is available in Outlook 2007.
This article provides reference documentation related to supported and unsupported HTML elements, attributes, and cascading style sheets properties.
Word 2007 HTML and CSS Rendering Capabilities in Outlook 2007 (Part 2 of 2) provides detailed instructions about how to install and use the Outlook HTML and CSS Validator tool.
The Outlook HTML and CSS Validator tool helps you to validate HTML and cascading style sheets grammar using some of the most popular Web development tools, such as Microsoft Office SharePoint Designer 2007, Microsoft Expression Web Designer 2007, Microsoft Visual Studio 2005, Macromedia Dreamweaver MX 2004, and Macromedia Dreamweaver 8.
These articles and accompanying tools are provided for your use and can help you to better understand the new capabilities offered with the switch to the Word 2007 HTML parsing and rendering engine. This information can help you with the generation of e-mail newsletters or other complex HTML documents.
Supported HTML Elements, Attributes, and Cascading Style Sheet Properties
Word 2007 supports a subset of the standard HTML 4.01 specification and of the Internet Explorer 6.0 HTML specification. Word 2007 also supports a subset of the standard Cascading Stylesheet Specification, Level 1. Word 2007 uses HTML elements that support a subset of the Word 2007 cascading style sheets properties. This article categorizes the Word 2007 supported cascading style sheets properties as follows:
FULL. The subset of the standard cascading style sheet 1.0 specification fully supported by Word. Note that Word 2007 also uses HTML elements that support a subset of the Word 2007 cascading style sheets properties.
COREEXTENDED. Two HTML elements that support a subset of the cascading style sheets properties are called out: DIV and P. DIV and P support a subset of Word 2007–supported cascading style sheet and are defined in this article by the term COREEXTENDED.
CORE. SPAN supports a smaller subset of Word 2007–supported cascading style sheets, defined by the term CORE.
Note: |
|---|
| For more information about the supported cascading style sheets property values in Word 2007, download and review the Outlook 2007 Tool: HTML and CSS Validator. |
Word 2007 HTML Specification
The following table provides a list of the supported HTML elements in Word 2007. Also included in the table is the cascading style sheets support for the specified element. For a complete list of cascading style sheets properties that Word 2007 supports, see the Word 2007 Cascading Style Sheet Specification.
Table 1. Word 2007 HTML elements, attributes, and associated cascading style sheet style support
| HTML Element | Attribute | Cascading Style Sheet Style Support Level |
|---|---|---|
|
a |
class href hreflang id name rel rev target shape style type urn | |
|
abbr |
class dir id lang style | |
|
acronym |
class dir id lang style | |
|
address |
class dir disabled id lang style | |
|
area |
class coords href id nohref shape style target | |
|
b |
class dir id lang style | |
|
base |
class href id target | |
|
basefont |
class color face id size style | |
|
big |
class dir id lang style | |
|
blockquote |
cite class dir id lang style | |
|
body |
alink background bgcolor bgproperties class id link nowrap text vlink | |
|
br |
class clear id style | |
|
caption |
align class id lang style valign | |
|
center |
class dir id lang style | |
|
cite |
class dir id lang style | |
|
code |
class dir id lang style | |
|
col |
align class id lang span style valign width | |
|
colgroup |
align bgcolor class dir id lang span style valign width | |
|
comment |
class data dir id lang style | |
|
dd |
class dir id lang style | |
|
del |
cite class datetime dir id lang style | |
|
dfn |
class dir id lang style | |
|
dir |
class dir id lang style type | |
|
div |
align class dir id lang nowrap style | |
|
dl |
class compact dir id lang style | |
|
dt |
class dir id lang style nowrap | |
|
em |
class dir id lang style | |
|
fieldset |
align class dir id lang style | |
|
font |
class color dir face id lang size style | |
|
frame |
allowtransparency application bordercolor class frameborder height id longdesc name src width |
None |
|
frameset |
border bordercolor class cols frameborder framespacing id |
None |
|
h1 |
align class dir id lang style | |
|
h2 |
align class dir id lang style | |
|
h3 |
align class dir id lang style | |
|
h4 |
align class dir id lang style | |
|
h5 |
align class dir id lang style | |
|
h6 |
align class dir id lang style | |
|
head |
dir lang |
None |
|
hr |
align class color dir id lang size style width | |
|
html |
dir lang |
None |
|
i |
class dir id lang style | |
|
img |
align alt border class dir dynsrc height hspace id ismap lang longdesc lowsrc name src style usemap vspace width | |
|
ins |
cite class datetime dir id lang style | |
|
kbd |
class dir id lang style | |
|
label |
class dir for id lang style | |
|
legend |
align class dir id lang style | |
|
li |
class dir id lang style type value | |
|
link |
class dir href hreflang id lang name rel rev style type | |
|
listing |
class dir id lang style | |
|
map |
class dir id lang name style | |
|
meta |
content http-equiv id name scheme |
None |
|
nobr |
class dir height id lang style | |
|
ol |
class compact dir id lang style type | |
|
p |
align class dir id lang style | |
|
pre |
class dir id lang style | |
|
s |
class dir id lang style | |
|
samp |
class dir id lang style | |
|
small |
class dir id lang style | |
|
span |
class dir disabled id lang style | |
|
strike |
class dir id lang style | |
|
strong |
class dir id lang style | |
|
style |
dir lang type |
None |
|
sub |
class dir id lang style | |
|
sup |
class dir id lang style | |
|
table |
align bgcolor border bordercolor cellpadding cellspacing class cols dir frame height id lang rules style summary width | |
|
tbody |
align bgcolor ch choff class cols dir id lang style valign | |
|
td |
abbr align axis bgcolor bordercolor ch choff class colspan datafld dir headers height id lang nowrap scope style width valign | |
|
textarea |
class cols dir id lang name readonly rows style wrap | |
|
tfoot |
bgcolor ch choff class cols dir id lang style valign | |
|
th |
abbr axis bgcolor bordercolor ch choff class colspan datafld dir headers height id lang nowrap scope style width valign | |
|
thead |
bgcolor ch choff class cols dir id lang style valign | |
|
tfoot |
bgcolor ch choff class cols dir id lang style valign | |
|
title |
class dir id lang style | |
|
tr |
align bgcolor bordercolor class dir height id lang style width valign | |
|
tt |
class dir id lang style | |
|
u |
class dir id lang style | |
|
ul |
class dir id lang style type | |
|
var |
class dir id lang style |
FULL |
|
xml |
class id src |
None |
Word 2007 Cascading Style Sheet Specification
The following section provides a list of the cascading style sheets properties that Word 2007 supports. The section organizes cascading style sheets properties into three groups: CORE, COREEXTENDED, and FULL. In Word 2007, certain HTML elements only support a subset of cascading style sheet properties.
CORE
The following cascading style sheet properties are supported:
-
color
-
font
-
font-family
-
font-style
-
font-variant
-
font-size
-
font-weight
-
text-decoration
-
background (only color)
-
background-color
-
text-align
-
vertical-align
-
letter-spacing
-
line-height
-
white-space
-
display
-
border
-
border-color
-
border-style
-
border-width
-
src
-
size
-
marks
-
page-break-before
-
page-break-after
-
page-break-inside
-
list-style
-
list-style-type
-
unicode-bidi
-
border-collapse
COREEXTENDED
All of CORE, plus the following cascading style sheet properties are supported:
-
text-indent
-
margin
-
margin-left
-
margin-right
-
margin-top
-
margin-bottom
FULL
All of CORE and COREEXTENDED, plus the following cascading style sheet properties are supported:
-
width
-
height
-
padding
-
padding-left
-
padding-right
-
padding-top
-
padding-bottom
-
border-left
-
border-right
-
border-top
-
border-bottom
-
border-left-color
-
border-left-width
-
border-left-style
-
border-right-color
-
border-right-width
-
border-right-style
-
border-top-color
-
border-top-width
-
border-top-style
-
border-bottom-color
-
border-bottom-width
-
border-bottom-style
Unsupported HTML Elements Compared with the HTML 4.01 Specification
The following is a list of top-level HTML elements that the HTML 4.01 specification supports, but that Word 2007 does not support. Note that Word 2007 considers unsupported HTML elements to be unknown elements.
Word 2007 does not support:
-
applet
-
bdo
-
button
-
form
-
iframe
-
input
-
isindex
-
menu
-
noframes
-
noscript
-
object
-
optgroup
-
option
-
param
-
q
-
script
-
select
Unsupported HTML Attributes Compared with the HTML 4.01 Specification
The following is a list of top-level HTML attributes that the HTML 4.01 specification supports, but that Word 2007 does not support. Note that Word 2007 considers unsupported HTML attributes to be unknown attributes.
Word 2007 does not support:
-
accept-charset
-
accept
-
accesskey
-
archive
-
background (only when there is a URL)
-
checked
-
classid
-
code
-
codecore
-
codetype
-
compact
-
data
-
declare
-
defer
-
disabled
-
enctype
-
longdesc
-
marginheight
-
marginwidth
-
media ( screen | print | projection | braille | speech | all )
-
method
-
multiple
-
noresize
-
object
-
onblur
-
onchange
-
onclick
-
ondblclick
-
onfocus
-
onkeydown
-
onkeypress
-
onkeyup
-
onload
-
onmousedown
-
onmousemove
-
onmouseout
-
onmouseover
-
onmouseup
-
onreset
-
onselect
-
onsubmit
-
onunload
-
readonly
-
scrolling
-
selected
-
standby
-
tabindex
-
title
-
valuetype
Unsupported HTML Elements and Attributes Compared with the HTML 4.01 Specification
Table 2 provides a list of all the HTML elements, along with the HTML attributes and attribute values, that Word 2007 does not support.
Table 2. Unsupported HTML elements and attributes
| Element | Attribute |
|---|---|
|
textarea |
cols |
|
td |
colspan=0 |
|
th |
colspan=0 |
|
frame |
frameborder=0 |
|
td |
rowspan=0 |
|
th |
rowspan=0 |
Unsupported Cascading Style Sheet Properties Compared with Cascading Style Sheets, Level 1
The following is a list of all the top-level cascading style sheet properties that the Cascading Stylesheet Specification, Level 1 supports, but that Word 2007 does not support. Note that Word 2007 considers unsupported cascading style sheet properties to be unknown properties.
-
background-attachment
-
background-image
-
background-position
-
background-repeat
-
clear
-
display
-
float
-
list-style-image
-
list-style-position
-
text-transform
-
word-spacing
Unsupported Cascading Style Sheet Properties Compared with Cascading Style Sheets, Level 2.1
The following is a list of all the top-level cascading style sheet properties that the Cascading Style Sheet Specification, Level 2.1 supports, but that Word 2007 does not support. Word 2007 considers unsupported cascading style sheet properties to be unknown properties.
-
azimuth
-
background-attachment
-
background-image
-
background-position
-
background-repeat
-
border-spacing
-
bottom
-
caption-side
-
clear
-
clip
-
content
-
counter-increment
-
counter-reset
-
cue-before, cue-after, cue
-
cursor
-
display
-
elevation
-
empty-cells
-
float
-
font-size-adjust
-
font-stretch
-
left
-
line-break
-
list-style-image
-
list-style-position
-
marker-offset
-
max-height
-
max-width
-
min-height
-
min-width
-
orphans
-
outline
-
outline-color
-
outline-style
-
outline-width
-
overflow
-
overflow-x
-
overflow-y
-
pause-before, pause-after, pause
-
pitch
-
pitch-range
-
play-during
-
position
-
quotes
-
richness
-
right
-
speak
-
speak-header
-
speak-numeral
-
speak-punctuation
-
speech-rate
-
stress
-
table-layout
-
text-shadow
-
text-transform
-
top
-
unicode-bidi
-
visibility
-
voice-family
-
volume
-
widows
-
word-spacing
-
z-index
Other Unsupported Web-Related Features
The following is a list of all other Web-related features that Word 2007 does not support:
-
Animated GIF images. Only a static representation of the GIF image shows.
-
Flash. Only a red "X" shows in the area where the flash would display.
Outlook 2007 Security Concerns
The following tags are reported as valid by the Outlook 2007 HTML and CSS Validator tool but are not actually permitted in Outlook 2007 e-mail because of security concerns:
-
Frameset
-
Frame
These tags are valid for Word 2007 content, but are intentionally blocked when it is used by Outlook 2007 because of security implications. Microsoft reserves the right to block certain tags that might compromise the privacy of users or the security of the e-mail content in which the content is displayed.
Conclusion
Use this article as a guide and reference when you create e-mail newsletters and other complex HTML documents so that they display in Outlook 2007. The Outlook 2007 Tool: HTML and CSS Validator provides a way to validate HTML and cascading style sheets grammar using some of the most popular Web development tools: Microsoft Office SharePoint Designer 2007, Microsoft Web Expressions 2007, Microsoft Visual Studio 2005, Macromedia Dreamweaver MX 2004, and Macromedia Dreamweaver 8. For more information about the Outlook 2007 Tool: HTML and CSS Validator, see Word 2007 HTML and CSS Rendering Capabilities in Outlook 2007 (Part 2 of 2).
We have tried to provide you with the most up-to-date and accurate information, but this document should not be considered a comprehensive reference guide. Please report technical inaccuracies you find to the Discussions in Word Mail newsgroup.
Acknowledgments
Thanks to Rob Little, Matt Scott, Terry Crowley, and Dan Costenaro for their contributions to this article.
Additional Resources
- 12/23/2011
- Lucky_Lu99
A brief moment of competence. My favorite element of unintended irony in this document is where you mention the "Internet Explorer 6.0 HTML specification"
As if such a thing existed. IE6, yeah, good times.
- 12/19/2011
- Tom von Alten
A few years ago, remember the Antitrust court case instructing them they could not distribute IE with some versions of Windows (which is just ludacris, who'd of thought it, an operating system with a browser built in, shock horror). But this has side effects, they couldn't rely on the HTML rendering engine being installed on all versions of Windows. The court no doubt gave them an short deadline to make this happen, so MS probably thought, errrr what do we do??? quick use Word.
The good solution of seperating out the html rendering engine out of IE is no doubt the future goal, but the two are probably very tightly coupled as when they designed it, it wasn't in the spec that they may be forced to remove IE from Windows.
That said, this was 2007, and its now 2011 going on for 2012 with no word of any plans to seperate IE's rendering engine.
- 12/1/2011
- marlon_tucker
Why isn't it possible to display html code correctly in a e-mail program in times of HTML5?
I sure hope there will be a patch or at least this will be corrected in the next version of Outlook - because it's driving me crazy.
- 11/17/2011
- platzhirsch
Even creating a simple HTML email in Outlook, a centered div of 600 pixels is not rendered properly. What, width is not supported? Are you really forcing us to go back to using TABLES for presentation?
<div style="width: 600px; margin-left: auto; margin-right: auto;">
TEST
</div>
</rant>
- 10/27/2011
- Gordon Bell
- 10/27/2011
- Gordon Bell
blockquote does not obey any css rules at all, regardless what way it gets set.
- 8/12/2011
- Zumitte
- 9/19/2011
- Thomas Lee
I have been a long standing user and fan of Microsoft products, and hope to remain so in the future.
I sometimes feel however that Microsoft is not interested in encouraging love for its products.
Microsoft's office products are widely used and very powerful, and as a result, we users live with them, at work, for a large part of our lives.
In living with them, we get to know their character and flaws, the good things, and the little frustrating limitations, we build our lives and work around them, and the functionality they offer, and come to rely on them as being consistent friends, from one version to the next.
It can therefore be of no surprise, that making sudden changes such as removing the IE HTML renderer (for whatever noble or internal reasons), comes as a physical shock to people - it hurts a lot - it generates a lot of anger - and it makes people want to rethink what they do.
We depend on you Microsoft; please do not abuse this trust.
For me, I am not a marketer, but the e-mail is now my letter, my business document, and I have come to use html to create well set out, sophisticated e-mails, containing detailed advice, which my clients (not all of whom use Microsoft products) expect from me.
A lot of my clients are walking around with iPads and the like as their primary tool - its a fact you have to accept - and so html e-mail is by far the best solution for them for sophisticated e-mails.
As part of this I also have a huge back-history of e-mails in our archive, all in HTML format.
And what can I expect if I upgrade to 2007/10-
- All my historical HTML e-mails may look ugly and mis-proportioned
- I will have to create simplistic e-mails to be sure they appear correctly, and reserve anything else for an attachment.
How is this an improvement?
Julian
- 6/10/2011
- Kungfuzi
So much for standards compliance, eh?
- 5/25/2011
- Andrew Becks
Oh and thanks for the validation tools. Popular???
"The Microsoft Office Outlook 2007 HTML and CSS Validator tool helps you to validate HTML and CSS grammar using some of the most popular Web developing tools such as Microsoft Office SharePoint Designer 2007, Microsoft Expression Web, Microsoft Visual Studio 2005, Macromedia Dreamweaver MX 2004 and Macromedia Dreamweaver 8."
I can't believe how much frustration and headache Microsoft continues to cause their customer base when they introduce new versions of their software, "claiming" to improve upon things when they only land themselves deeper into a hole of hated dug by these same customers. You've wasted us thousands of hours of time in time that we'll never get back in failed attempts to make what looks PERFECT by HTML standards absolultely horrible, like it was thrown in a blender, turned on high for 30 seconds, and called "WORD HTML".
GET RID OF IT!
Word HTML is by far the WORST, most NON-STANDARDS complain attempt at HTML in the development realm today. Wake up and look at the feedback from your customers and partners, like myself.
- 4/30/2011
- thetootall
- 4/30/2011
- thetootall
- 4/28/2011
- countart
Now, I'm looking at telling them that what they want is impossible, or writing a massive php file with a nightmare in RegEx to convert their template pages (which they are creating and I have no power over the content of) from valid (I hope) web pages, to valid e-mails.
It's bad enough I have to try to get them making valid HTML pages for in the browser. I can't honestly expect them to check each element against a list. These aren't IT people, nor web developers. Most of them would be using guess-and-check and a WYSIWYG client to put together pages. It's one thing to have to capture external css and writing it into a Style tag. It's quite another to have to magically predict what they mean with certain elements so that I can write a 'smart' program that translates it all into 1990's HTML.
All in all, I'm really not satisfied with the quality of Outlook 2007's HTML/CSS rendering, and I would hope that future versions do not repeat this mistake. I would expect MS e-mail clients to match MS IE in rendering capabilities. It would present professionals with the ability to keep a consistent branding across web mediums with ease. I understand that the general person with few computer skills and young children should be able to make e-mails; I'm not arguing against that (since, as far as I can tell, those are the only people benefiting here), but those people are likely to not have a whole lot invested in their e-mail displaying correctly.
However, giving them perfect rendering compared to MSWord (which I believe was the point?) at the expense business professionals seems a poor move to me. The former is going to care for maybe 60 seconds that their text might not have stayed the same size and shade of teal. The latter is going to put in the hours and the money to get it right... and they are going to care for a lot longer than 60 seconds when it goes wrong.
Sure, you can argue that past mail clients won't understand if you change it and people start making their e-mails fancier. The same argument could be used against putting data on DVD instead of CD, CD instead of 3.5in Floppy Disk, 3.5in floppy disk instead of 8in floppy disk, etc, etc. Considering the only 8in floppy I own is used as a book mark in a giant art history text, I'm sure you can see the point.
In short, this 'choice' is costing businesses money. From a logical perspective, it is unlikely to make MS more money than if it functioned as expected.
- 3/30/2011
- Raine Dragon
- 3/23/2011
- Amtiskaw
Who would use Word to edit any HTML email anyway? The word is NOT meant for HTML editing for God's sake! I was considering buying Office 2010 before, but now I know better what to do. I would not support a company that could care less about their users.
- 10/21/2010
- FrancesW
Wake up and smell the CSS
- 10/18/2010
- Eriknsd
click on print, i get 3 sheets, first one blank, second one cover about 1/20th of the content on the page.
it's not hard. seriously.
- 9/30/2010
- J. Albert Bowden II
- 8/27/2010
- Esther Fan
- 9/1/2010
- Esther Fan
I have several templates created using this spec. (The spec was helpful thank you.)
http://commadot.com/the-holy-mail/
http://commadot.com/cross-client-html-email-v2/
http://commadot.com/email-best-practices/
I have noticed a very specific problem. (Blogged: http://commadot.com/outlook-to-gmail-formatting-annoyance/)
The problem is that an image used like this:
<img src="http://www.site.com/images/foo.gif">
gets rendered like this:
<p class="msoNormal"><img src="cid:23490234"></p>
I don't care about the image being embedded. What freaks me out is the <P> tag! It's creating artificial margins above all the images. This sucks. Gmail strips CSS classes so the class is useless. Even purely from Outlook-to-Outlook this gets messed up.
I need to figure out a way to make the <P> tag constrained in height regardless of its margins. What options do I have? Could someone from Microsoft please explain why you are making my life a living ***?
Thanks, Glen Lipka
Esther Fan, MSFT: Thank you for your feedback. Please submit this to Microsoft Connect or the forums so that it can be reviewed and addressed by the product team.
Microsoft Connect: http://connect.microsoft.com
MSDN Forum: http://social.msdn.microsoft.com/Forums/en-US/categories
- 6/24/2009
- GlenLipka
- 8/27/2010
- Esther Fan
Now I understand why Microsoft is so afraid of Linux and the world of open source. The alternatives to Microsoft just got a whole lot more attractive...
After spending almost a week trying to un-css my e-mails I'm giving up and telling people to use Thunderbird instead if they want to read my messages. Oh but that's right, Thunderbird doesn't work reliably with Microsoft Exchange because Microsoft didn't bother to implement IMAP properly...
Esther Fan, MSFT: Thank you for your feedback. Please submit this to Microsoft Connect or the forums so that it can be reviewed and addressed by the product team.
Microsoft Connect: http://connect.microsoft.com
MSDN Forum: http://social.msdn.microsoft.com/Forums/en-US/categories
- 1/28/2010
- Adam Nielsen
- 8/27/2010
- Esther Fan
<p class="editorial important first"></p>These can then be accessed through CSS through the appropriate selectors. So with the above example all three of these style rules should be applied to the paragraph:
p.editorial {
font-family:'Times New Roman';
}
p.important {
border: 1px red solid;
}
p.first {
font-weight:bold;
}Outlook and Word do not recognise this however (I presume they naïvely assume that class can only have one value) and will only apply the styles relating to the initial class name listed in the attribute (in this case "editorial").
[1] http://www.w3.org/TR/html401/struct/global.html#h-7.5.2
Esther Fan, MSFT: Thank you for your feedback. Please submit this to Microsoft Connect or the forums so that it can be reviewed and addressed by the product team.
Microsoft Connect: http://connect.microsoft.com
MSDN Forum: http://social.msdn.microsoft.com/Forums/en-US/categories
- 6/30/2010
- James Hardy
- 8/27/2010
- Esther Fan
The WHOLE point of HTML email is that it renders the SAME as browser content. There is no more risk opening an email than opening a web page so WHAT WERE YOU THINKING.
The CEO of our company is ALREADY leaning toward open source, do you REALLY have to HELP HIM!!!
This is the worst idea coming out of MS since Vista.
It is not too late to fix this..... can you say SERVICE PACK !!!!
Esther Fan, MSFT: Thank you for your feedback. Please submit this to Microsoft Connect or the forums so that it can be reviewed and addressed by the product team.
Microsoft Connect: http://connect.microsoft.com
MSDN Forum: http://social.msdn.microsoft.com/Forums/en-US/categories
- 3/21/2010
- Donald Burr
- 8/27/2010
- Esther Fan
What is the point?
I have a wonderful HTML signature which used W3C Valid XHTML 1.0 Transitional and CSS2 to recreate our company logo without using a picture. It even displays the same in both IE and firefox. Of course since Word doesnt support DIV positioning or floats it will no longer work in outlook, which we all use.
Why take such an enormous step backwards instead of fixing the HTML incompatibility in Word? You have alienated a huge number of users to please just a few. Newsflash - Most users are not interested in using Word to create email signatures, due to the enormous bloat.
Most annoyed, at this non sensical approach.
- 1/13/2009
- Pensive1
- 8/15/2010
- Thomas Lee
http://cot.ag/9yG1Xm
- 7/22/2010
- BThies
- 8/15/2010
- Thomas Lee
That would be like someone commenting about the problems associated with a Car part that was recalled 3 years ago. The real question is "Does Office 2010" have the same HTML rendering problems?
If it does.... OK I SAY WE STAGE A REVOLUTION...
If it doesn't well then.. we all just need to get over it!!! and agree that software changes...
- 6/15/2010
- Darkriderdesign
With IE9 doing everyhting it can to conform to standards, why would Microsoft let this occur in Outlook?
- 4/16/2010
- -SG-
1. Too much has been sacrificed to provide consistency between Word and Outlook for the group of users that will do complicated styling in an Outlook email.
2. Emails do not need the robust styling options of a Word document and generally benefit from the simpler choices of Rich Text Formatting.
3. Any document needing both complicated styling and to be emailed will be created in Word and emailed as an attachment.
4. An organization can often add to a standard such as W3C CSS but rarely can it take away.
5. Many organizations will change their HTML emails to conform to this decision but many more will not because an email address alone doesn’t inherently indicate whether they are using Outlook or not.
My one request would be to allow developers to override the layout engine used. A tag in the <head> section would be all it’d take to get Outlook 2007 (and 2010) to use the Internet Explorer/Trident/MSHTML layout engine. Word would still be the default but it could be overriden with something like:
<meta name="layoutengine" content="MSHTML" />
I believe most of this fussing would go away if a choice like that existed.
- 4/2/2010
- joeeckberg
- 4/2/2010
- joeeckberg
- 3/24/2010
- Sol Design
- 2/26/2010
- Elemenopy
Too bad only developers read these posts and not users.
I don't understand why all the free email clients work and outlook doesn't, I feel like I'm owed an explanation. (but don't expect one)
- 1/28/2010
- Nick Yeoman
- 12/11/2009
- Juan Capristán
- 11/20/2009
- disgruntled_developer_hates_microsoft
Many extra hours of checking my newsletter html to work in Outlook 2007, no, no, no!
- 11/12/2009
- EtienneBa
This has to be the most backward, ill-thought product to ever hit the enterprise.
Font tags and tables, yippee! Party like it's 1999.
- 8/29/2009
- atomicPete
I'm just adding my name to the list of disgruntled companies on this page. Leaving out GIF animation is utterly incompetent and inexcuseable. Quoting from your knowledge base (http://support.microsoft.com/kb/320314) :
<quote>
Advantages:
- GIF is a widely supported Internet standard.
- Lossless compression and transparency are supported.
- Animated GIFs are prevalent and easy to create with many GIF animation programs.
</quote>
We look forward to the patch release coming out soon. Meanwhile we suffer the cost of re-coding *all* our subscriber email newsletter templates to be compatible with Outlook 2007, and re-drawing all our gifs.
- 5/14/2009
- MaxMcConnell_PromptCommunications
- 5/29/2009
- Thomas Lee
When I read this that Outlook 2007 dont support the basic CSS any more, I am so relifed that I not use any microsoft products any more.
One and a half year ago I bought an Dell with Vista Ultimate and Office 2007. 3 months later I was so unsatisfied with Vista and Office 2007. Products that are almost impossible to use.
And now when I am trying writing an HTML newsletter, and read this that Outlook 2007 have the rendering engine from Microsoft Office Word 2007, why change an working system. Why can't Microsoft do any thing new that is userfriendly and that works in an common business.
Now an happy none Microsoft user
- 5/4/2009
- Marcus B
- 3/28/2009
- jordanvanbergen
- 5/1/2009
- Thomas Lee
Why does this article claims that Outlook 2007 support margins, without any sidenote about margin around images?
Same goes for alignments of images. You can align images, but then you loose the surrounding style, unless you repeat it again....
Anyway, to me it's *** and impossible to automaticly produce high quality newsletters who will look good in Outlook 2007.
Why Microsoft? Why?
- 11/27/2008
- marijn01
- 4/30/2009
- Thomas Lee
What I'd honestly like to see is some sort of article that states a few things. What it's not going to state is what Outlook/Word 2007 DOES support, and what it CAN do, but why it CAN'T seem to do something that nearly every other modern email client CAN. It's going to state why you guys decided NOT to go down the road of standards, and why you guys decided to make it extremely hard on developers/designers like myself. And then...it's going to state a solution. A patch, a REALLY BIG patch, along with an apology for not taking your stance as a leader in the technical industry seriously.
Free browsers can manage to do what MS can't, and that's get things right. And that's when I just have to ask: Were you just not thinking? Is there ANY reason at all that this had to happen like this?
BTW, I'm running Vista, and think that you guys have the potential to put out a product that EVERYONE will be pleased with (and a huge advantage over Apple with your market share). I have had minimal problems with Vista, and none of them being MS's fault. I've got to admit that the UAC is annoying, but I can deal with changing a setting or two.
- 11/3/2008
- J53
- 4/30/2009
- Thomas Lee
Let's have a look at the options for HTML rendering: a) a web browser, b) a word processor. Hands up if you choose 'b'...
...looks like you're the only one in the room with your hand up, MS. Good job.
- 11/3/2008
- beejamin
- 4/30/2009
- Thomas Lee
We face with a 30K messages/day service, similar bad email rendering, like all other community members below, do. The only solutions we have identified so far, is to either use multipart/alternative (not really ergonomic), or to simplify the email template until it also renders good in OL2007. With a complete QA cycle of course : /
- 4/30/2009
- Dimitri Pochet
Anyway, the symptom is that fieldset is not displayed at all and legend is displayed as text or as it is. I tried to add the simplests tag like <fieldset></fieldset> inside body tag to more expressed case like adding style="border:1" tag, but there is no change at all.
Is there any way to show <fieldset> or a way to get around this problem? By the way, does someone in Microsft developer tested before they release outlook 2007 to create this support docuement?
- 2/2/2009
- Ablemike
- 4/21/2009
- Thomas Lee
- 3/18/2009
- Confus3d
Here is a good place page that you (Microsoft Developers) should go check out.
http://www.molly.com/2007/01/18/what-happened-with-html-and-css-in-outlook-2007/
This is not a small problem and is now affecting business that support your products. I'm really hoping that you come up with a fix for this. If not you are just pushing people into using web based e-mail. All of which support HTML and CSS in the e-mails.
PLEASE fix this problem!
- 1/20/2009
- Frustrated Developer Over Here
Dear Developers,
I have heard and read about the limitations you have implemented within office 2007.
This new code-limitations to MS Outlook will have big negative impact within the creation and publication of e-mail advert campaigns.
As you know by today most of the e-mail promotional campaigns contain various visual elements. The new unsupported HTML tags as TABLES and BACKGROUND-IMAGES are essential tools within the "already very limited" capabilities of the existing e-mail clients.
With this new changes you are:
1. stopping an important established standard and support of the Outlook e-mail client.
2. Contributing to unnessesary confussion and problems within preestablished standards.
Outlook is an important and established communication tool within different branches world wide.
In this sense cutting down its features won't make it much attractive and compatible to anyone.
Please be aware of all concequences involved within this limitations.
I therefore expressevely request to remove this limitations which are not needed.
Thanks a lot for considering this request and critic.
Kind Regards
M.G.
Switzerland
- 11/20/2008
- mangonzo
