Here's the summary as of right now.

1. There is an issue with the order of CSS files when using the dnn:styles skin object. Gemini issue here
2. There is an issue with the order of *anything* you put in the page head by using the DNN page-level settings. Gemini issue here.

There is no JS-specific ordering issue that I'm aware of. To be clear though, if you put JS in your page head, then you may have an ordering issue. But that would be the same with CSS. Anything in the DNN page settings "head" text-box will be loaded *above* any other CSS/JS.

The issue is that in DNN 6.1 all of the CSS/JS files that are loaded through our new API are being loaded below page-level head content and dnn:styles content. This was not intentional and it will be corrected in the next release. I do not have knowledge of a time-frame or any influence over the timeframe even, but just know that we're working on it and we recognize this is very important.

The immediate workaround is to remove any JS/CSS that is having issues from the page head  in your DNN page settings, or to use DnnCssInclude instead of the styles skin object. More documentation on using the new controls/API is found here: Client Resource Management in DNN 6.1

Ian

---

Good tip David.

Regarding priority - If multiple items share the same priority they are loaded in the order that they were requested during the asp.net page lifecycle which can sometimes basically appear like it's random from an outside perspective.

Ian

---