Discussions
order of <head> add-ons
Is it just me? Or does anyone else think it's ass-backwards to have a template's "add to <head>" block come first, before the theme's "add to <head>" block when the page is rendered?
I mean... really?
If I want to override a site-wide CSS rule in a particular class of pages, I don't see a way to do it, except by putting the <link> or <style> element in the <body>, which violates the HTML spec.
If I want to include, say, the jQuery lib and use it in a particular way on a particular class of pages, I have to include jQuery in the template. I can put <script> elements in the <body>, I suppose, and in that way keep the jQuery include in the theme's <head>. But that's just kind of messy.