Fair enough. I understand the point, I think, except that I don't think you gain anything at all by it, except more complexity in the site's file structure. Every hack now represents one more file that has to be uploaded, version controlled, backed up, managed etc.
If your file management workload is directly proportional to the number of files you manage (and we are talking no more than 50 extra files in most cases) then I think it's time you you invest in some tools to streamline your processes.
I'd have thought it was simpler to have the hack actually in the main css
file, and commented adequately so it was easy to find there. Or am I
missing the point?
My compromise is to place all hacks for [insert your favourite buggy browser] into it's own CSS file.
CSS hack techniques are forever changing. CSS fundamentals are set in stone.
-- tim lucas
http://www.toolmantim.com
*****************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
*****************************************************
