Seconded -- compared to all the other hacks you'll need to make when coding for IE browsers, conditional comments are the least of your worries; in fact they are your friend!
On 02/07/07, Nick Gleitzman <[EMAIL PROTECTED]> wrote:
On 2 Jul 2007, at 6:09 PM, Sarah Peeke (XERT) wrote: > I guess I was hoping to fix the problem(s), rather than just rely on a > hack. Other suggestions appreciated. Fair enough, but I'd say your chances of getting the one set of css rules to display correctly in all browsers are pretty slim - especially if you want to include browsers as flawed as Exploder 5.x. Even MS themselves accept how hard this is - hence CCs. I routinely serve as many as three alternative stylesheets vis CCs for different versions of IE. They only need to contain a handful of rules necessary to override the correct values served to compliant browsers. Whether you consider CCs a hack is, I guess, subjective. But your code will validate, and they're easy to remove with a global search and replace if and when the time comes that you don't need them any more. Why beat your head against the wall of buggy browsers when the manufacturer themselves supplies a workaround? N ___________________________ omnivision. websight. http://www.omnivision.com.au/ ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
-- David Little -e: [EMAIL PROTECTED] -w: www.littled.net ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************