<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: CSS &amp; Troubleshooting IE6</title>
	<atom:link href="http://www.kimberlyblessing.com/archive/2009/07/21/css-troubleshooting-ie6/feed" rel="self" type="application/rss+xml" />
	<link>http://www.kimberlyblessing.com/archive/2009/07/21/css-troubleshooting-ie6</link>
	<description>KBlog by Kimberly Blessing</description>
	<lastBuildDate>Tue, 31 Jan 2012 12:40:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Megan</title>
		<link>http://www.kimberlyblessing.com/archive/2009/07/21/css-troubleshooting-ie6#comment-20378</link>
		<dc:creator>Megan</dc:creator>
		<pubDate>Thu, 30 Jul 2009 20:29:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.kimberlyblessing.com/?p=420#comment-20378</guid>
		<description>I almost never validate my CSS. That&#039;s something that&#039;s never been important to me, for some reason. I guess because I don&#039;t find a lot of ways that CSS would become invalid.

I think the other important thing to remember about hacks is to document which hack you&#039;re using, for which browser(s), and why. It could be that the problem goes away when old browsers are depreciated and yet the hack stays in there because nobody can remember what it was for.

Thanks for coming out and saying that it&#039;s okay not to be valid (for the right reasons!). I know some people will actually switch to a transitional doctype when they intentionally do something minor that&#039;s invalid. Or if they can&#039;t be sure that someone won&#039;t make a mistake that invalidates the code. I&#039;ve always thought that it&#039;s better to be strict - even if you can&#039;t verify that it will always be valid. I know my blog sometimes becomes invalid because I forget to encode ampersands in URLs.</description>
		<content:encoded><![CDATA[<p>I almost never validate my CSS. That&#8217;s something that&#8217;s never been important to me, for some reason. I guess because I don&#8217;t find a lot of ways that CSS would become invalid.</p>
<p>I think the other important thing to remember about hacks is to document which hack you&#8217;re using, for which browser(s), and why. It could be that the problem goes away when old browsers are depreciated and yet the hack stays in there because nobody can remember what it was for.</p>
<p>Thanks for coming out and saying that it&#8217;s okay not to be valid (for the right reasons!). I know some people will actually switch to a transitional doctype when they intentionally do something minor that&#8217;s invalid. Or if they can&#8217;t be sure that someone won&#8217;t make a mistake that invalidates the code. I&#8217;ve always thought that it&#8217;s better to be strict &#8211; even if you can&#8217;t verify that it will always be valid. I know my blog sometimes becomes invalid because I forget to encode ampersands in URLs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Jundt</title>
		<link>http://www.kimberlyblessing.com/archive/2009/07/21/css-troubleshooting-ie6#comment-20373</link>
		<dc:creator>Kevin Jundt</dc:creator>
		<pubDate>Thu, 23 Jul 2009 05:27:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.kimberlyblessing.com/?p=420#comment-20373</guid>
		<description>Hey Kimberly ... I don&#039;t disagree and, in fact, would like to add that even widely used libraries like YUI use hacks in their CSS files.  You can imagine what a nightmare it would be to get your audience to include multiple files for each component just to handle all the hacks in a standards based way!  Your library would end up not being so widely used...

There&#039;s also a performance impact.  The more connections you make, the slower your page loads.  Sure, it&#039;s only for IE but, alas, that&#039;s still the majority of users.  At PayPal, there was a core style sheet but only a single set of IE specific style sheets.  At a site as large as PP, this could lead to some serious bloat.  If all the IE specific code went into these files, every page is going to have to parse all the IE specific rules for the entire site even if you only need one.

Still, one should try...</description>
		<content:encoded><![CDATA[<p>Hey Kimberly &#8230; I don&#8217;t disagree and, in fact, would like to add that even widely used libraries like YUI use hacks in their CSS files.  You can imagine what a nightmare it would be to get your audience to include multiple files for each component just to handle all the hacks in a standards based way!  Your library would end up not being so widely used&#8230;</p>
<p>There&#8217;s also a performance impact.  The more connections you make, the slower your page loads.  Sure, it&#8217;s only for IE but, alas, that&#8217;s still the majority of users.  At PayPal, there was a core style sheet but only a single set of IE specific style sheets.  At a site as large as PP, this could lead to some serious bloat.  If all the IE specific code went into these files, every page is going to have to parse all the IE specific rules for the entire site even if you only need one.</p>
<p>Still, one should try&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>


