A speculative thought: Would it be that the universal margin and
padding declaration get in the way because it has highest specificity?
* {margin: 0; padding: 0;}
I only started using it very recently in three sites but two of them
didn't require me to use extra classess for padding and margin.
tee
Working on this site, I notice that there is an isue with class,
span class specificities that the above three browsers wont' honor
and which never happened before with other sites I did.
For example:
#content {}
#content p {padding: 10px; }
say, I wanted the last paragraph to have 20px padding-bottom
instead of 10px.
I added this:
.lastpara {padding-bottom: 20px; }
It won't works (note, didn't test it on PC' IEs at that stage ),
but if I change my code to :
#content p.lastpara { padding-bottom: 20px; }
Safari, Firefox and Opera honored my request.
<div id="content">
<p> first paragraph</p>
<p class="lastpara">last paragrap</p>
Despite the lower specificities for class, I would think the world
three most advanced browsers would honor my simple request without
telling them specifically that the '.lastpara' is the child of the
'p' element of descendant of 'content' div.
But I am too fatigue to figure out why.
tee
***************
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
