http://kickasswebdesign.com/wordpress/2007/03/hacks-for-various-flavors-of-ie/ Kickass info re CSS, WordPress Themes, ModX Templates, CubeCart Templates, CMS Templates, WebDev News, and occasional weird personal observations. Fri, 08 Aug 2008 20:55:21 +0000 http://wordpress.org/?v=2.5.1 http://kickasswebdesign.com/wordpress/2007/03/hacks-for-various-flavors-of-ie/#comment-6316 My take on IE7; meet the new bugs, same as the old bugs Sun, 24 Jun 2007 16:39:43 +0000 http://kickasswebdesign.com/wordpress/2007/03/hacks-for-various-flavors-of-ie/#comment-6316 [...] I know some purists will argue that using conditional comments is hacky and awful, since conditional comments are a proprietary call and browser specific code, and thise purists would rather use one stylesheet and more wacko IE specific filters, but in my estimation hacks are hacks no matter where they are, and I’d rather put the good and true css in the main stylesheet and the bugbusting version for IE in a separate and easily findable area. This will, hopefully, futureproof my sites in a better way, and allow me latitude if IE8 either gets it right or, as is sadly to be expected, introduces a new crop of bugs to the old, since it will allow me to correct the conditional comment call to “if lte IE 7″ and feed IE8 its own bugbuster stylesheet. It was not fun going back into some of the old sites and fixing for IE7, even though I was more or less prepared. Anything I can do to make a future IE8 transition easier will be a GOOD thing, especially since I’ll have that many more sites in my portfolio by then, and that many more clients to look out for. [...] [...] I know some purists will argue that using conditional comments is hacky and awful, since conditional comments are a proprietary call and browser specific code, and thise purists would rather use one stylesheet and more wacko IE specific filters, but in my estimation hacks are hacks no matter where they are, and I’d rather put the good and true css in the main stylesheet and the bugbusting version for IE in a separate and easily findable area. This will, hopefully, futureproof my sites in a better way, and allow me latitude if IE8 either gets it right or, as is sadly to be expected, introduces a new crop of bugs to the old, since it will allow me to correct the conditional comment call to “if lte IE 7″ and feed IE8 its own bugbuster stylesheet. It was not fun going back into some of the old sites and fixing for IE7, even though I was more or less prepared. Anything I can do to make a future IE8 transition easier will be a GOOD thing, especially since I’ll have that many more sites in my portfolio by then, and that many more clients to look out for. [...]

]]>