I would say the recommendation should be to use wp_enqueue_style on secondary et al. stylesheets leaving the standard "primary" style.css to be continued as it is commonly found now.<br><br>Essentially, as I understood the idea, this is to better implement conditional stylesheets more than anything else ... <br>
<br><br>Cais.<br><br><div class="gmail_quote">On Thu, Apr 21, 2011 at 6:51 PM, esmi at quirm dot net <span dir="ltr"><<a href="mailto:esmi@quirm.net">esmi@quirm.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
on <a href="tel:21%2F04%2F2011%2023" value="+12104201123" target="_blank">21/04/2011 23</a>:07 Otto said the following:<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The problem is that stylesheet order doesn't actually matter. CSS is<br>
all about specificity of the definitions.<br>
</blockquote>
<br></div>
<snip><br>
<br>
Order *does* matter. Take two identical rules in separate sheets and the later one takes priority. That's how child themes work, after all. :-)<br>
<br>
I take your point about specificity but I've got themes that use html in some rules. and given that I tend to be pretty specific when writing CSS anyway, some of them could be damn hard to over-write using pure specificity. I'd argue that there still have to be mechanisms available for plugin authors, developers, users etc to load later sheets.<br>
<br>
Mel<div><div></div><div class="h5"><br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</div></div></blockquote></div><br>