Gunlaug Sørtun wrote: > The real reason for me to not use 'CC' for separation, is that the > versioning goes on on HTML level and adds unnecessary garbage to every > single page.
If you happen to be designing an XHTML site and decide you want to use server-side scripting to deliver your pages as XHTML/xml-application to standards-compliant browsers and as HTML/text to MSIE, then you can selectively include your various Conditional Comments into only the HTML, dumbed-down-for-MSIE version. Then the "unnecessary garbage" CC's will not even show up in your "pristine" XHTML/CSS version. This is probably not that practical in most real-world cases, but it does take the separation idea to its logical conclusion. And for those who really want "pristine", separated code, it is a viable solution. I like the CC method because it is easy to understand and it should be easy for a different developer to understand five years from now. CSS hacks, on the other hand, require a bit of arcane knowledge that may be difficult to understand for a newbie five years from now, even with explanatory comments added. But I agree with Gunlaug that the down-side of CC's is that it requires adding unnecessary garbage to every single X/HTML page's head section. Phil. ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
