PDA

View Full Version : Background Image in Table does not display


Minerva23
01-09-2007, 03:35 AM
Hi all

I'm creating a html page for an email to be sent out as an invite, i've created a table and included a background image. After i've done everything (text, alignment,etc), the image is able to be seen when i preview it on Dreamweaver.

When i transfer it to the stationary folder in Microsoft Outlook and do a test run, the image comes out when it is in the compose page, however when i receive the email the image does not display.

Any of you have any ideas on why this is happening?
If you could help with this problem it will be great since i'm on a tight deadline.

Thanks!

Ricky55
01-09-2007, 08:31 AM
Are you sure this is nothing simple like Outlook is setup to receive plain text emails and not HTML formatted emails.

There are also options in outlook that prevent images from being displayed have you checked all this obvious stuff?

Ricky55

chriskq
01-09-2007, 10:43 AM
use absolute links.

without posting ur code its harder to tell but im guessing ur image is referenced such as: <table style="background: url(images/bg.gif) no-repeat 0 0;">

when it should be background: url(httP://www.uploadsiteHere/images/bg.gif)

domedia
01-09-2007, 01:36 PM
Welcome to the forums Minerva!

The reason you have to do what chrisq is suggesting is that the image has to be available to the receiver. Right now the email is pointing to the C: drive.

Minerva23
01-10-2007, 06:59 AM
Hi domedia & chriskq

Your suggestion worked!
Thanks!

Cheers!

davidj
01-10-2007, 08:07 AM
while we are on this topic i came across this from sitepoint

Microsoft Breaks HTML Email Rendering in Outlook 2007

If support for web standards in browsers is improving slowly, then support in email clients is moving at a glacial pace. Attempts to document things like CSS support in the major email clients (http://www.campaignmonitor.com/blog/2006/03/a_guide_to_css_support_in_emai.html) have revealed a depressing state of affairs, but with recent desktop clients like Thunderbird (http://www.mozilla.com/thunderbird/) now sitting on solid rendering engines, things have been looking up.
All that changed when Microsoft dropped a lump of coal into every web developer's stocking with the end-of-year release to business customers, and the upcoming consumer release, of Outlook 2007 (http://office.microsoft.com/outlook/).
At the risk of turning this newsletter into a biweekly Microsoft bash, Redmond has done it again. While the IE team was soothing the tortured souls of web developers everywhere with the new, more compliant Internet Explorer 7, the Office team pulled a fast one, ripping out the IE-based rendering engine that Outlook has always used for email, and replacing it with ... drum roll please ... Microsoft Word.
That's right. Instead of taking advantage of Internet Explorer 7, Outlook 2007 uses the very limited support for HTML and CSS that is built into Word 2007 to display HTML email messages.

http://i2.sitepoint.com/g/nl/tt/ol2007-tt.jpg

Having tested the two public beta versions of Outlook 2007 late last year, I knew there was something screwy going on. Many of the newsletters I subscribed to had become unreadable, and SitePoint's own publications (including the Tech Times) were looking decidedly unhealthy. I dutifully reported these rendering issues with the feedback mechanisms provided in the beta, and wrote them off as Internet Explorer 7 integration issues that would be resolved in the final release.

But late last month, a thread in the SitePoint Forums (http://www.sitepoint.com/forums/showthread.php?t=446030) caught my eye. Microsoft had published a pair of articles (http://msdn2.microsoft.com/en-us/library/aa338201.aspx) describing the support for HTML and CSS in Outlook 2007, and the news wasn't good: "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."
The limitations imposed by Word 2007 are described in detail in the article, but here are a few highlights:

no support for background images (HTML or CSS)
no support for forms
no support for Flash, or other plugins
no support for CSS floats
no support for replacing bullets with images in unordered lists
no support for CSS positioning
no support for animated GIFsIn short, unless your HTML emails are very, very simple, you're going to run into problems with Outlook 2007, and in most cases the only solution to those problems will be to reduce the complexity of your HTML email design to accommodate Outlook's limited feature set.
With the release of Outlook 2007, Microsoft is effectively adding an entirely new rendering engine to the mix—one that designers producing HTML email will not be able to ignore.
Not only that, but this new rendering engine isn't any better than that which Outlook previously used—indeed, it's far worse. With this release, Outlook drops from being one of the best clients for HTML email support to the level of Lotus Notes and Eudora, which, in the words of Campaign Monitor's David Grenier (http://www.campaignmonitor.com/blog/2006/03/a_guide_to_css_support_in_emai.html), "are serial killers making our email design lives hell."
Why on earth would Microsoft do such a thing? Security? Microsoft has been shouting from the rooftops about the new security model in Internet Explorer 7 that prevents the nasty security issues that have plagued Outlook in the past. It seems Microsoft doesn't buy its own publicity, however, because this move sends the message that Internet Explorer's security model is not to be trusted.
Where to from here? Well, as a first step, you'll want to use Microsoft's handy-dandy tool (http://msdn2.microsoft.com/en-us/library/aa338200.aspx) to tell you which parts of your lean, mean HTML emails need to be replaced with old-fashioned HTML sludge. As a second step, you may want to consider giving your Outlook-based readers an easy way to switch to text-only email.