Mac CSS problem

I've got a fairly simple stylesheet that works fine on the PC side,
IE6, NS, Opera, and FireFox.

On the Mac, it looses the styles part way through the stylesheet.
(JigSaw warns on no generic font-family and no color when background
color is specified.) This happens in Safari, Netscape and IE.

Rearranging the stylesheet fixes everything. ie, changing the order
of the styles. I normally order styles from the top of the page down.

Why would the Mac complain?

Jeff

Michael Vilain wrote:

In article <Jzjig.3833$lf4.3746 (AT) newsread1 (DOT) news.pas.earthlink.net>,
Jeff <dont_bug_me (AT) all (DOT) uk> wrote:


I've got a fairly simple stylesheet that works fine on the PC side,
IE6, NS, Opera, and FireFox.

On the Mac, it looses the styles part way through the stylesheet.
(JigSaw warns on no generic font-family and no color when background
color is specified.) This happens in Safari, Netscape and IE.

Rearranging the stylesheet fixes everything. ie, changing the order
of the styles. I normally order styles from the top of the page down.

Why would the Mac complain?

Jeff


URL of "bad page"?

Found it.

I had two id's of the same name. Curiously these were the last
definitions in the "bad" stylesheet (footer). Moving them up fixed this
in the Mac and the PC didn't care. Odd how much damage it did.

Validator found it, I had made some changes in the layout and hadn't
deleted the old container.

<URL: http://69.20.29.70/testBAD.html >

Thanks,
Jeff

Jeff wrote:

I've got a fairly simple stylesheet that works fine on the PC side,
IE6, NS, Opera, and FireFox.

On the Mac, it looses the styles part way through the stylesheet.
(JigSaw warns on no generic font-family and no color when background
color is specified.) This happens in Safari, Netscape and IE.

Rearranging the stylesheet fixes everything. ie, changing the order
of the styles. I normally order styles from the top of the page
down.

That took me a few passes to grok properly. What I think you mean is, "I
normally declare the rules in the stylesheet in the order in which they
are used in some HTML page", appproximately. That still doesn't make
perfect sense, but it makes more sense to me than writing the stylesheet
backwards (or something), which was the first meaning I extracted!

It is a mistake to declare stylesheet rules in some arbitrary order,
because the order of declaration is significant in CSS. Rules declared
later in a stylesheet take precedence over rules earlier in a
stylesheet. Therefore the order of declaration of CSS rules should be
determined by the way those rules are supposed to interact, not by some
kind of "neatness" requirement.

--
Jack.