<?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"
	>
<channel>
	<title>Comments on: External CSS won&#8217;t load in IE7</title>
	<atom:link href="http://www.daniel-skinner.co.uk/external-css-wont-load-in-ie7/05/04/2008/feed" rel="self" type="application/rss+xml" />
	<link>http://www.daniel-skinner.co.uk/external-css-wont-load-in-ie7/05/04/2008</link>
	<description>Daniel Skinner's Blog: Web Development news and articles</description>
	<pubDate>Thu, 20 Nov 2008 21:53:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Daniel Skinner</title>
		<link>http://www.daniel-skinner.co.uk/external-css-wont-load-in-ie7/05/04/2008#comment-185</link>
		<dc:creator>Daniel Skinner</dc:creator>
		<pubDate>Tue, 06 May 2008 14:58:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.daniel-skinner.co.uk/external-css-wont-load-in-ie7/05/04/2008#comment-185</guid>
		<description>Yes, it's strange. Actually, I ended up taking @charset “UTF-8″; out in the end as it invalidated the CSS file.

Yeah, strict doctypes can have an effect on the CSS, for example, the box model. However, I have always found less issues when coding to strict.</description>
		<content:encoded><![CDATA[<p>Yes, it&#8217;s strange. Actually, I ended up taking @charset “UTF-8″; out in the end as it invalidated the CSS file.</p>
<p>Yeah, strict doctypes can have an effect on the CSS, for example, the box model. However, I have always found less issues when coding to strict.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pkenjora</title>
		<link>http://www.daniel-skinner.co.uk/external-css-wont-load-in-ie7/05/04/2008#comment-184</link>
		<dc:creator>pkenjora</dc:creator>
		<pubDate>Tue, 06 May 2008 14:45:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.daniel-skinner.co.uk/external-css-wont-load-in-ie7/05/04/2008#comment-184</guid>
		<description>I had similar issues for a while, my solution was to include the W3C header at the top of my pages.  



I think strict is preferred but I needed loose for some weird css or something.</description>
		<content:encoded><![CDATA[<p>I had similar issues for a while, my solution was to include the W3C header at the top of my pages.  </p>
<p>I think strict is preferred but I needed loose for some weird css or something.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
