Thanks Dennis,
I have a resolution. And as you would expect it has nothing to do with anything. (see below)
You've at least answered one other nagging question I had: "which configuration works best in the Win environment?"
Clearly it' s the downloaded version (ie
background-image: url(images/bac.jpg);) which is what one would expect .
But that means Safari is fine (so score one for the OS formally known as beleaguered) and that Firefox is somehow not conforming to standard
.
Just thinking that hurts my open source sensibilities.
Plus it behaves the same on the original FF 1.0 release and the current 1.06. Mozilla org has this cute feature whereby one cannot have any Extensions without first installing the latest. And I just had to have Web Developer (utterly wonderful) without which I wouldn't have been able to figure half of this stuff out.
reversing
background: #CD9967;
background-image: url(images/bac.jpg);
to read
background-image: url(images/bac.jpg);
background: #CD9967;
results in both Safari and Firefox not displaying bac.jpg
Well, ok. since as you say, parameter order is critical, that makes sense.
But it got me thinking (a dangerous thing). What if I put the background-image line as the absolute last item in the body{...} declaration?
Lo and behold that worked!
Yay! Much celebrating and drinks for everyone bartender!
Until (uh oh)
I opened the "Edit CSS" sidebar in Firefox.
And the BG image went away.
Merciful heavens it has nothing to do with nothing. Its an odd anomaly in the Firefox Web Developer Extension since closing "Edit CSS" makes the BG pop right back in.
What was that I said about Web Developer Extension (ver 0.9.4) being utterly wonderful?
\
and
It makes the ganglia twitch I tell you!
so moving that line didn't do much of anything at all I suspect.
I ain't touchin' it.
Any bets that his doesn't happen on the Win side of things?
Thanks for spurring my curiosity so that this foolishness finally revealed itself to me.
Hope you found the story amusing.
jje