Edmedia, it is in the current version of dotnetnuke.

---

Cuong Dang
Co-founder: Enliven, dnnGallery
LinkedIn | Twitter
I'm the author of DNN and Web Standards Wrox Blox

As Steve Jobs would say, "This is b********".

I think having a default.css included in the website is wrong. Why do regular users and visitors have to download an unnecessary file. This is the wrong approach.

If someone has edit privileges, load these files, else, do not.

On top of that, overriding generic tags inside default.css, such as body, ul and li instead of using custom selectors is doubly wrong.

If anything, web development is in an entirely different stratosphere... how does DNN's approach help facilitate using techniques such as using reset definitions and so on? In short, it doesn't. At the moment you have default.css, portal.css, skin.css, container.css, and various module.css stylesheets. This is insane.

I really hope DNN turns around and starts to adopt and support commonly used techniques. 

Is this beta css supposed to be able to replace the current default.css? I tried replacing it but just ended up with missing styles for all of the administration elements like login, the administrative toolbar, and popups for editing were all messed up.