Christopher Schultz-2 wrote: > > You're right in that @import appears to serialize CSS fetching in many > browsers, and that's bad. On the other hand, why not use Steve's > suggestion and use the LINK LINK technique? > > Presumably you have separate stylesheets for a reason. Why not keep them > separate? > > As usual, I agree with Hassan's suggestion that you map > /assets/css/concat/global.css to the JSP servlet and use JSP in your > dynamic stylesheet if you've already decided to use JSP. > >
Sorry if you thought I was blunt in my answer and the links I pointed to did not make it clear that by reducing HTTP requests and avoiding imports, amongst other performance techniques, a user will experience a faster web site. I am using <link> to load stylesheets. When developing, I prefer to keep style sheets separate, e.g. layout.css, typography.css, content.css, header.css, etc... This is beneficial especially when working as part of a team with source control. Smaller files are more manageable than one, single large file. For production though, as few files as possible is desirable to reduce the number of HTTP requests. Thanks for your help everyone. -- View this message in context: http://www.nabble.com/How-to-use-Includes-in-CSS-files-tp26024235p26063842.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
