If possible, it'd be nice to include each view's CSS separately, so that we don't have the weight of the jQuery UI CSS in the main view.
One issue with that is that Rotator doesn't yet (I don't think) take a dependency on a version of DNN that has the client resource management functionality (i.e. DNN 6.1). It still might be good to include those manually (I think if we call CDefault.AddPageStyleSheet, it will end up getting routed to the client resource manager, if on DNN 6.1+).
We recently ran into an issue with a site that had CSS combination turned on, where Rotator's CSS caused the CSS to run into IE 9's selector limit, making some of the CSS no longer apply.
If possible, it'd be nice to include each view's CSS separately, so that we don't have the weight of the jQuery UI CSS in the main view.
One issue with that is that Rotator doesn't yet (I don't think) take a dependency on a version of DNN that has the client resource management functionality (i.e. DNN 6.1). It still might be good to include those manually (I think if we call
CDefault.AddPageStyleSheet, it will end up getting routed to the client resource manager, if on DNN 6.1+).We recently ran into an issue with a site that had CSS combination turned on, where Rotator's CSS caused the CSS to run into IE 9's selector limit, making some of the CSS no longer apply.