Header image behind my logo?

[Steel Rat]

Funny, I had commented out the two lines in the stylesheet which referred to the header_bg, but IE was still showing it, even though all was kosher in FF.

Even stranger, view source in IE did not have any reference to header_bg in the file. So it was displaying it, but wasn't part of the source?? It wasn't a cacheing issue either. I had to actually delete the two lines for IE to play nice.

I hate IE.

[kuroi]

Funny, I had commented out the two lines in the stylesheet which referred to the header_bg, but IE was still showing it, even though all was kosher in FF.

Even stranger, view source in IE did not have any reference to header_bg in the file. So it was displaying it, but wasn't part of the source?? It wasn't a cacheing issue either. I had to actually delete the two lines for IE to play nice.

I hate IE.

View source wouldn't show any reference to the header_bg as it is in an external stylesheet not the source.

The usual reason for the other symptoms that you described is using the wrong type of comment for a stylesheet, i.e. using either a php or HTML comment. FF tends to be very nice about this and play along anyway, but IE treats it as an error and ignores your attempts to make it a comment.

[Steel Rat]

Hmm, if the image is being displayed how can it not be part of the source?

I used // as a single line comment, like a java comment, since CSS seems to use that notation, such as /* */ for multi-line.

I can still hate IE

[Steel Rat]

Hmm, if the image is being displayed how can it not be part of the source?

I used // as a single line comment, like a java comment, since CSS seems to use that notation, such as /* */ for multi-line.

I can still hate IE

But now that I look at it, I can see that happening.

So what is the proper single-line comment for CSS?

[kuroi]

But now that I look at it, I can see that happening.

So what is the proper single-line comment for CSS?

It's /* comment */

[kuroi]

Hmm, if the image is being displayed how can it not be part of the source?

The image is part of the styling applied to the source. This separation of source (aka content) from styling (aka presentation) lies at the heart of current best practise in web design.

[Steel Rat]

The image is part of the styling applied to the source. This separation of source (aka content) from styling (aka presentation) lies at the heart of current best practise in web design.

Gotcha. Makes sense, but it does make things a bit harder to troubleshoot. for me, anyway.

I'm still a Tables man. Can't stand the flightiness of Divs, and how they often fail to constrain content much of the time.

[Kim]

I'm still a Tables man. Can't stand the flightiness of Divs, and how they often fail to constrain content much of the time.

Aw... but, you do not have to give up the tables totally. Only use them where absolutely neccessary. Use the CSS backgrounds with the table(s) for fabulous effects. (that is how the rounded corner frames are done on this site)

[Steel Rat]

Aw... but, you do not have to give up the tables totally. Only use them where absolutely neccessary. Use the CSS backgrounds with the table(s) for fabulous effects. (that is how the rounded corner frames are done on this site)

I'm still figuring that out, lol. I did add a bg to the centercolumn on my site via CSS (just a png created in Fireworks. So I know the concept.) It would be nice, however, if IE would join the 21st century and retain transparency on PNGs. Don't know if IE7 does or not.

[kuroi]

It would be nice, however, if IE would join the 21st century and retain transparency on PNGs. Don't know if IE7 does or not.

IE7 does. You're going to have to hate it a little less now