I'm with Mike on this. I don't see a benefit. In fact, when I read the article it looked like more work to me :
1. Hacks in main CSS file - Hack gets outdated, edit CSS file and remove hack
2. Hacks in separate CSS file - Hack gets outdated, edit CSS file and remove import, then delete separate hack file
There is an extra step. No huge difference, so I'd be willing to do it for a benefit, but I just don't see one. If (and I think this is what Mike was asking) anyone can demonstrate a potential benefit from this process, please enlighten me (us)
Cheers, Lachlan
Your way: open css file, search thru (possibly) 100s of lines of code to locate hack, double-check selector so you're removing the hack on the right declaration, repeat, rinse, save and close, upload.
My way: open css file, delete one @import rule (line #1), save, close, upload. Delete css hacks file.
There may be an extra file involved, but I know which is faster...
Nick ___________________________ Omnivision. Websight. http://www.omnivision.com.au/
*****************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
*****************************************************
