FW->DW->CSS-P

NOt all browsers default to a white background color. If you don't specify
one, you get the default.

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"KKreps" <webforumsuser (AT) macromedia (DOT) com> wrote

Bonnie, Thanks for the suggestion. No, I actually was unaware that the
content
div needed a background specified. I added a white background, but I don't
see
any difference. Would you please let me know what browser you are using
where
this problem had been obvious? Or please explain why a background is
always
needed for this situation? Thanks. I'm eager to learn. KK

KKreps wrote:

Bonnie, Thanks for the suggestion. No, I actually was unaware that the content
div needed a background specified. I added a white background, but I don't see
any difference. Would you please let me know what browser you are using where
this problem had been obvious? Or please explain why a background is always
needed for this situation? Thanks. I'm eager to learn. KK

Karen,

This is a trick I learned from DiMa and Nadia: I have my default
background in Firefox set to a bright color--otherwise it's hard to
notice when the background is not defined. I don't know how likely it
is that nondevelopers would define their background as some other color
(it would never have occurred to me), but I have also heard that (even
if no one ever touched their browser preferences), you'll get grey as a
deault background color on some Macintoshes).

It's funny how many otherwise professional looking sites (at least on
the "outside" don't have the background color defined--it's actually a
little annoying for me because it's really hard to read, say, bright
blue against the bright pink I chose, but it's hard not to notice and so
a problem easy to diagnose.

--
Bonnie in Alameda
kroko at
sbcglobal dot net
http://www.theanimalrescuesite.com/cgi-bin/WebObjects/CTDSites.woa

Bonnie in Alameda wrote:

KKreps wrote:

Bonnie, Thanks for the suggestion. No, I actually was unaware that
the content div needed a background specified. I added a white
background, but I don't see any difference. Would you please let me
know what browser you are using where this problem had been obvious?
Or please explain why a background is always needed for this
situation? Thanks. I'm eager to learn. KK

Karen,

This is a trick I learned from DiMa and Nadia: I have my default
background in Firefox set to a bright color--otherwise it's hard to
notice when the background is not defined. I don't know how likely it
is that nondevelopers would define their background as some other color
(it would never have occurred to me), but I have also heard that (even
if no one ever touched their browser preferences), you'll get grey as a
deault background color on some Macintoshes).

It's funny how many otherwise professional looking sites (at least on
the "outside" don't have the background color defined--it's actually a
little annoying for me because it's really hard to read, say, bright
blue against the bright pink I chose, but it's hard not to notice and so
a problem easy to diagnose.

It is good to define your background color, but the last grey background
I saw on my macintosh was netscape 4.7 ... (so don't worry.)

Joost Kolkman