the way 1.8 is designed is that specific CSS is only called when you're on a specific page like groups for example. instead of having the CSS for groups in one single global CSS file, it's only called once ;) this is why 1.8 is faster than 1.7. at least this is from my point of view.
the way 1.8 is designed is that specific CSS is only called when you're on a specific page like groups for example
This is false for the most part, individual views can call a css include - usually for specific things like jquery modules that require css where it doesn't make sense to aggregate that into the main css.
For the most part all of the individual css.php files you see get aggregated into the global css much the same as they did in 1.7
thanks for the clarification, i've been gone fishing in alaska for a while now and i wasn't around to see elgg 1.8 being released. yes the css.php for a plugin is integrated into the global css which is true but there are special lines of code to include a specific css into a view which is what i like about 1.8
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by Raül Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.