The ordering of requirements CSS and JScript is a constant cause of headaches for me, the only long-term solution will be to add a "priority" to them I think.

For now though, you should be able to get the css to appear at the end of the requirements stack by putting it in your classes controller init function:

I've had to use this technique to implement conditional comments for IE6/7 etc.

hope that does the trick

EDIT: of course search is in the page controller ... you might get away with putting it in the results() function.

Rich

In this case I usually just use more specific selectors in searchResults than layout, its not like javascript where you'll get undefined errors. CSS cascades fine if you simply use more specific selectors.

Because of how the template parser works I would have thought it have included the ones at the top of the page in a top down approach. Sounds like a bug. I like implementing a priority value (1-100) is a bit too much for this sort of thing.

If you're trying to use "searchResults.css" to override styles that are in one of the other stylesheets, then you will need to place it at the bottom of the call stack.

Browsers read and use both CSS and JavaScript in the order their called. This is why you get "undefined" errors if you call a jQuery extension before calling the base jQuery pack. In the case of CSS, the browser just renders what it finds and if it finds another call that affects an element in a later call, then it simply overwrites the previous call.

The cascading in CSS goes as follows:

For styles called in the same level (say, in external stylesheets), the last call takes precedence.
For styles called in different levels, the read order is: external stylesheet, embedded stylesheet, inline style (with each one overriding the one before, so inline styles always overwrite everything else)
More specific styles overwrite less specific styles, so "a { color: blue; }" will be overwritten by ".nav a {color: red; }" will be overwritten by ".nav #top a {color: green;}"