Forum Moderators: not2easy
#########
<style type="text/css">
#pid p {width:300px;}
p.pclass {width:500px;}
.pclass {width:150px}
</style>
</head>
<body>
<div id="pid">
<p class="pclass">Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Vestibulum ac tellus eu turpis tempor pharetra. Fusce eget odio id mauris volutpat accumsan.</p>
############
You would expect the text to be 150px as thats the last one in the flow?order? thing, but the #pid p overules it. Same as an inline styles would overide all the other styles.
Whats that called?
Nevermind found it.
Calculating a selector's specificity [w3.org]
you seem set against CSS (from other recent posts in the CSS section), I doubt there is use in commenting on people who find the answer to their problem within the limited time they have to edit their own post.
Specificity is part of CSS, learning about it is part of learning about CSS. The link posted by appi2 actually points to the standard itself.
Those confused perhaps need to learn more and eventually see the light, that's all.
If you read even more of my posts, you'd see the opposite is true.
You are seeing my frustration. That's because this learning curve is killing me.
In the past I learned Unix, Perl, SAS (a database), Networking while managing a million dollar project for an investment bank, and it took about a month or two for me to provide a major deliverable that another major corporation could not deliver in 3 years...
However, learning css has taken much longer than the above and I hate how long it's taking. I know I'll get it one day. But I'm kind of a perfectionist, and when you learn that some of your code might not be so good, you want to go back to all your clients and redo it, even though it tests fine.
Ok, I'll take it as frustration.
But the frustration should not be with CSS in all honesty. Most of the problems come from the browers that implement only parts of the standard, or implement it plainly broken, or just refuse to correct their plain out bugs and call them features to be propagated to next versions. Some of the vendors seem much more interested by implementing pars of CSS3 while they are still not doing things in CSS1 comme-il-faut.
CSS is like an artform, where the combination of various pieces will render entirely different results than the combination of others.
Good point Doc. I was never an artist. The graphic artists don't want to know code and developers don't want to know from design, but are forced to. Not an easy thing for either side to get the other...
