Beau wrote:
James Ellis said:
You could also divide your stylesheet up into different files - one for navigation, one for layout, one for headings etc etc - then link (or however you do it) them all in.
I would have thought that from a general performance perspective, splitting the CSS into too many files would be a bad idea, since each one is going to require an extra HTTP Request/Response to download. That extra traffic will cost you bytes (and time), so if you need all that CSS on the page, you may as well have it all in one file.
A few hundred bytes at the _very_ most. Considering that most of the time you won't be loading blog.css, screenreader.css, projector.css, print.css and whatever else, you will be saving that transfer time and data easily. In a world of 56K modems even, 300 bytes (let's say you're sending a LOT of http headers [and for a stylesheet why would you?]), would still take under 0.04 seconds to transfer and in a world of broadband, that's even less. Considering that each stylesheet that you won't be loading up will probably contain more than 300 bytes, it's probably more sensible to split it up.
Besides, it makes for more manageable CSS when you want to edit it.
--
/----------------------------------------------------------------------\
|Adam Carmichael, A+, 2xMCP (Windows 2000), Cert IV Helpdesk Admin |
|[EMAIL PROTECTED] /( _,-----,_ )\ _| |_ /,|| |
|#1 Computer Services \`/ \'/ _| |_ || |
|BSD/UNIX & Cisco Network Engineer\ /,\ /,\ / | | _||_ |
\----------------------------------------------------------------------/
*****************************************************
The discussion list for http://webstandardsgroup.org/
*****************************************************
