<?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: Swearing Off Hacks with Conditional Comments</title>
	<atom:link href="http://geek.focalcurve.com/archive/2005/09/swearing-off-hacks/feed/" rel="self" type="application/rss+xml" />
	<link>http://geek.focalcurve.com/archive/2005/09/swearing-off-hacks/</link>
	<description>Pyrotechnics erupt in the distance. Guitar solo.</description>
	<lastBuildDate>Thu, 22 Jan 2009 02:20:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Craig</title>
		<link>http://geek.focalcurve.com/archive/2005/09/swearing-off-hacks/comment-page-1/#comment-873</link>
		<dc:creator>Craig</dc:creator>
		<pubDate>Thu, 22 Sep 2005 21:04:18 +0000</pubDate>
		<guid isPermaLink="false">http://geek.focalcurve.com/archive/2005/07/to-hack-or-not-to-hack/#comment-873</guid>
		<description>Alas, Ted, conditional comments are HTML, not CSS. They have to go in the document. The extra markup is the biggest drawback in my book.

If your site uses some sort of template so the document header is contained in one file (which is then included on every page of the site) it&#039;s pretty simple to add a comment in that one place, and then to remove it at some time when it no longer becomes neccessary.

However, if you&#039;re maintaining pages by hand I&#039;d still opt for CSS-only hacks over conditional comments. And in that case I do recommend moving all your hacks to the end of the file and grouping them together, rather than leaving them scattered throughout a style sheet.</description>
		<content:encoded><![CDATA[<p>Alas, Ted, conditional comments are HTML, not CSS. They have to go in the document. The extra markup is the biggest drawback in my book.</p>
<p>If your site uses some sort of template so the document header is contained in one file (which is then included on every page of the site) it&#8217;s pretty simple to add a comment in that one place, and then to remove it at some time when it no longer becomes neccessary.</p>
<p>However, if you&#8217;re maintaining pages by hand I&#8217;d still opt for CSS-only hacks over conditional comments. And in that case I do recommend moving all your hacks to the end of the file and grouping them together, rather than leaving them scattered throughout a style sheet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted Drake</title>
		<link>http://geek.focalcurve.com/archive/2005/09/swearing-off-hacks/comment-page-1/#comment-872</link>
		<dc:creator>Ted Drake</dc:creator>
		<pubDate>Thu, 22 Sep 2005 20:29:49 +0000</pubDate>
		<guid isPermaLink="false">http://geek.focalcurve.com/archive/2005/07/to-hack-or-not-to-hack/#comment-872</guid>
		<description>Can conditional comments sit inside the CSS file? It would be nice to move all of my ie hacks to the end of the file rather than import them as an additional style sheet.</description>
		<content:encoded><![CDATA[<p>Can conditional comments sit inside the CSS file? It would be nice to move all of my ie hacks to the end of the file rather than import them as an additional style sheet.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
