I was trying to make the blockquotes stand out a little better by removing the color change. I opted for a border style just on the top and bottom. When I use the border statements (last three), I lose my font-family.
Interesting...
DIV.body BLOCKQUOTE
{
BACKGROUND-COLOR: steelblue;
FONT-FAMILY: "courier new";
FONT-STYLE: normal;
FONT-SIZE: 9pt;
margin-right: 0;
PADDING-BOTTOM: 1%;
PADDING-TOP: 1%;
padding-left: 1%;
padding-right: 1%;
border-style:groove;
border-top-width: thin;
border-bottom-width: thin;
}
I've changed your 4.77 version to use lightsteelblue background with tahoma 10pt and blockquote background to lightyellow with courier new 9pt.Sorry. I'd love to take credit but it belongs to steveegg. I'd love to see what you're doing though. I suspect my color and wallpaper choices are a little lame. I'm just demonstrating the principles. I hope some others will come up with better visuals and let me know about them so I can post better ones for everyone.
I was trying to make the blockquotes stand out a little better by removing the color change. I opted for a border style just on the top and bottom. When I use the border statements (last three), I lose my font-family.A lot of times, it a tag is unknown or in some way broken, it will "eat" the one that follows. So, if NS4.77 choked on steelblue in BACKGROUND-COLOR, it might eat the FONT-FAMILY. As I understand it, the color names are now considered bad style and we're supposed to specify the colors directly.
DIV.body BLOCKQUOTE
{
BACKGROUND-COLOR: steelblue;
FONT-FAMILY: "courier new";
...
When I use the border statements (last three), I lose my font-family.Netscape 4.7x doesn't accept borders (in fact, it really fouls things up if you pair, say, an outset and inset). One thing to add to GWB's response; it looks like there's no space between the colon and the groove in your posting of the DIV.body BLOCKQUOTE.