Am Nov 16, 2007 um 16:29 schrieb [EMAIL PROTECTED]:
I dislike code based on brower-checking because maintenance and testing becomes difficult. Simple CSS updates need to change several files; did the newly hired developer remember?
I feel different about this. Keeping hacks (only hacks) separated is IMO a healthy thing. The readability of the main css file is good as it does not contain any hacks (pure valid css). The hack-stylesheet is separated and can be deleted when a browser becomes obsolete.
Remembering hacks and there consequences inside a stylesheet is hard (and the hack removal might even influence the modern compliant browsers as they «see» the hacks as well).
The separation using conditional comments is especially handy when it comes to testing - it is well defined which browser reads the stylesheet. And for non Microsoft-Browsers... only a comment.
Jürgen Jürgen Ragaller null-oder-eins GmbH Zürich [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
