On Mon, 07 Apr 2008 23:21:26 +0200
Ingo Chao wrote:
Michael Adams wrote:
...
Then you have four factors involved which should be taken into
account in the following order: weight, origin, specificity, sort
order. But you didn't ask about them
CSS 2.1:6.4.1 -4 says:
if two
tedd wrote:
John wrote:
Any suggestions on a spot on line with a good explanation of the
cascading relationship(s)?
This is a simplistic explanation of the cascade [1].
I would not discourage anyone from attempting to learn anything as
complex as the cascade.
I have been using CSS for a couple years now, but most of what I've
done is emulate code I've seen and bang it into the form I need it to
be.
Often this works mostly, but then a certain situation or another's
computer will reveal embarrassing rookie mistakes.
In addition to simply racking
John wrote:
Any suggestions on a spot on line with a good explanation of the
cascading relationship(s)?
For a complete picture I think the source is best...
http://www.w3.org/TR/CSS21/cascade.html#cascade
regards
Georg
--
http://www.gunlaug.no
John,
From my personal experience, I first always recommend others take a look
over at HTMLDog (1) and get to know the tutorials going on there.
Second thing I always aim for is consistent markup through your pages. If
you're building each webpage with a different naming structure, you can't
John wrote:
I have been using CSS for a couple years now, but most of what I've
done is emulate code I've seen and bang it into the form I need it to
be.
Often this works mostly, but then a certain situation or another's
computer will reveal embarrassing rookie mistakes.
In addition
Gunlaug Sørtun wrote:
John wrote:
Any suggestions on a spot on line with a good explanation of the
cascading relationship(s)?
For a complete picture I think the source is best...
http://www.w3.org/TR/CSS21/cascade.html#cascade
I'm afraid specifications (or draft specifications) aren't
On Mon, 07 Apr 2008 12:13:52 -0700
John wrote:
I have been using CSS for a couple years now, but most of what I've
done is emulate code I've seen and bang it into the form I need it to
be.
Any suggestions on a spot on line with a good explanation of the
cascading relationship(s)?
A
Michael Adams wrote:
...
Then you have four factors involved which should be taken into account
in the following order: weight, origin, specificity, sort order. But you
didn't ask about them
CSS 2.1:6.4.1 -4 says:
if two declarations have the same weight, origin and specificity, the
John wrote:
I have been using CSS for a couple years now, but most of what I've
done is emulate code I've seen and bang it into the form I need it to
be.
Often this works mostly, but then a certain situation or another's
computer will reveal embarrassing rookie mistakes.
In addition
Ingo Chao wrote:
CSS 2.1:6.4.1 -4 says: if two declarations have the same weight,
origin and specificity, the latter specified wins.
This sounds clear, but ... what exactly is meant by weight?
Weight itself is a conceptual thing in the cascade, and a weight is only
larger, smaller or
11 matches
Mail list logo