<?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: Taking Conditional Comments Too Far</title>
	<atom:link href="http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/feed/" rel="self" type="application/rss+xml" />
	<link>http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/</link>
	<description>A resource for Web designers and developers to read about and discuss their craft.</description>
	<lastBuildDate>Wed, 28 Jul 2010 19:29:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Dave</title>
		<link>http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/#comment-1393</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Sun, 05 Aug 2007 10:24:43 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/#comment-1393</guid>
		<description>Sorry if you find this off topic. However I think this can be a good tip if we can solve it.

I use conditional events too. However I have run into a problem with it.

I have two seperate css files for IE7 and IE6 in my online portfolio located at http://cssfreeancer.awardspace.com .

IE6 mysteriously using IE7&#039;s css file in addition to it&#039;s specific css file. This causes IE6 not to render the page as intended in some cases such as the shadow of the bg pic in the header and div in &quot;about portfolio&quot; section.

When I disable the other.css file which is for browsers other than IE6, then IE6 is just fine. Problem occures when other.css file is enabled.

Have you guys run into the same problem before? could somebody help to solve this please?

thanks in advance.</description>
		<content:encoded><![CDATA[<p>Sorry if you find this off topic. However I think this can be a good tip if we can solve it.</p>
<p>I use conditional events too. However I have run into a problem with it.</p>
<p>I have two seperate css files for IE7 and IE6 in my online portfolio located at <a href="http://cssfreeancer.awardspace.com" rel="nofollow">http://cssfreeancer.awardspace.com</a> .</p>
<p>IE6 mysteriously using IE7&#8242;s css file in addition to it&#8217;s specific css file. This causes IE6 not to render the page as intended in some cases such as the shadow of the bg pic in the header and div in &#8220;about portfolio&#8221; section.</p>
<p>When I disable the other.css file which is for browsers other than IE6, then IE6 is just fine. Problem occures when other.css file is enabled.</p>
<p>Have you guys run into the same problem before? could somebody help to solve this please?</p>
<p>thanks in advance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/#comment-1397</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Mon, 30 Jul 2007 01:35:47 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/#comment-1397</guid>
		<description>I use conditional comments exactly as you do. I have an &quot;ie6hacks.css&quot; and an &quot;ie7hacks.css&quot; that get included into nearly every site I design via conditional comments. I&#039;ve never even considered putting them into the body (I just made sure a friend of mine didn&#039;t do that last week, as I showed him the conditional comment technique). I find conditional comments far better than the * html hack, and IE7 introduced it&#039;s own set of problems when working with CSS, even aside from its predecessor, IE6.</description>
		<content:encoded><![CDATA[<p>I use conditional comments exactly as you do. I have an &#8220;ie6hacks.css&#8221; and an &#8220;ie7hacks.css&#8221; that get included into nearly every site I design via conditional comments. I&#8217;ve never even considered putting them into the body (I just made sure a friend of mine didn&#8217;t do that last week, as I showed him the conditional comment technique). I find conditional comments far better than the * html hack, and IE7 introduced it&#8217;s own set of problems when working with CSS, even aside from its predecessor, IE6.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie</title>
		<link>http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/#comment-1396</link>
		<dc:creator>Jamie</dc:creator>
		<pubDate>Thu, 26 Jul 2007 12:59:16 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/#comment-1396</guid>
		<description>I dislike conditional statements, they make the developer do the work of the browser. What I would like to se is standards compliance in browsers, but we can&#039;t hope for miracles right?

In my view, XHTML is there to markup content, CSS is there to style it and Javascript is there to make the content do pretty things. If there is a standard content should be marked up to that standard, if everyone stopped jumping hoops for IE then hopefully market forces would work and consumers would vote with their feet and start using standard compliant browsers.

If you really want conditional statements then use a server side method, it is far more powerful and all the ugly hacks are hidden away.</description>
		<content:encoded><![CDATA[<p>I dislike conditional statements, they make the developer do the work of the browser. What I would like to se is standards compliance in browsers, but we can&#8217;t hope for miracles right?</p>
<p>In my view, XHTML is there to markup content, CSS is there to style it and Javascript is there to make the content do pretty things. If there is a standard content should be marked up to that standard, if everyone stopped jumping hoops for IE then hopefully market forces would work and consumers would vote with their feet and start using standard compliant browsers.</p>
<p>If you really want conditional statements then use a server side method, it is far more powerful and all the ugly hacks are hidden away.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julie Hathaway</title>
		<link>http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/#comment-1387</link>
		<dc:creator>Julie Hathaway</dc:creator>
		<pubDate>Tue, 24 Jul 2007 12:41:38 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/#comment-1387</guid>
		<description>I always use a conditional comment to link to an IE-specific stylesheet, even if the stylesheet only contains one stupid rule, such as a height declaration to mimic min-height. I do this because I want to make it as obvious as possible how ridiculous IE is (&quot;see what it takes to make IE behave?&quot;). I find this perversely satisfying.

Up until now my CCs have only gone in the head, though. Phil&#039;s idea of using them to advertise FF is terrific. :)</description>
		<content:encoded><![CDATA[<p>I always use a conditional comment to link to an IE-specific stylesheet, even if the stylesheet only contains one stupid rule, such as a height declaration to mimic min-height. I do this because I want to make it as obvious as possible how ridiculous IE is (&#8220;see what it takes to make IE behave?&#8221;). I find this perversely satisfying.</p>
<p>Up until now my CCs have only gone in the head, though. Phil&#8217;s idea of using them to advertise FF is terrific. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: All in a days work&#8230;</title>
		<link>http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/#comment-1391</link>
		<dc:creator>All in a days work&#8230;</dc:creator>
		<pubDate>Tue, 24 Jul 2007 04:17:03 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/#comment-1391</guid>
		<description>[...] Taking Conditional Comments Too Far When you choose to use conditional comments in the body of your document, you’re electing to alter the DOM in a more significant way. Now, instead of working with different style sheets to solve a problem, you’re altering the problem itself. [...]</description>
		<content:encoded><![CDATA[<p>[...] Taking Conditional Comments Too Far When you choose to use conditional comments in the body of your document, you’re electing to alter the DOM in a more significant way. Now, instead of working with different style sheets to solve a problem, you’re altering the problem itself. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/#comment-1392</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Tue, 24 Jul 2007 02:42:58 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/#comment-1392</guid>
		<description>I must admit, the comments offered here have opened my eyes to some circumstances which hadn&#039;t crossed my mind before.

@Calvin: In my opinion, that can be deemed acceptable use of conditional comments in your source.  You&#039;ve done a nice favor towards those not using IE.

@Phil: Yes, including an ad for Firefox specifically aimed at IE users.  You&#039;re right, there&#039;s definitely a gray area here.  Like everything, it can be taken to an extraordinary level for sure.

@Luke:  That&#039;s a creative use I haven&#039;t seen in the wild before.  As far as conditional comments and JavaScript are concerned, I was simply referring to wrapping the &lt;code&gt;&lt;script&gt;&lt;/code&gt; snippet within a conditional comment to ensure that it was only Internet Explorer taking the time to request the file at all.

Thanks to you guys for offering your opinions on the matter!</description>
		<content:encoded><![CDATA[<p>I must admit, the comments offered here have opened my eyes to some circumstances which hadn&#8217;t crossed my mind before.</p>
<p>@Calvin: In my opinion, that can be deemed acceptable use of conditional comments in your source.  You&#8217;ve done a nice favor towards those not using IE.</p>
<p>@Phil: Yes, including an ad for Firefox specifically aimed at IE users.  You&#8217;re right, there&#8217;s definitely a gray area here.  Like everything, it can be taken to an extraordinary level for sure.</p>
<p>@Luke:  That&#8217;s a creative use I haven&#8217;t seen in the wild before.  As far as conditional comments and JavaScript are concerned, I was simply referring to wrapping the <code>&lt;script&gt;</code> snippet within a conditional comment to ensure that it was only Internet Explorer taking the time to request the file at all.</p>
<p>Thanks to you guys for offering your opinions on the matter!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luke</title>
		<link>http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/#comment-1388</link>
		<dc:creator>Luke</dc:creator>
		<pubDate>Tue, 24 Jul 2007 02:05:14 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/#comment-1388</guid>
		<description>I definitely prefer conditional comments to use of css hacks.  Similar to the method Phil linked to on PIE, I&#039;ve recently taken to using a single conditional comment block wrapping the open body tag, assigning a class=&quot;IE [IE ver]&quot;.  This allows me to use the cascade to override style rules in a single style sheet as needed per whichever version of IE is creating mayhem in whatever fashion.

I haven&#039;t used conditional comments in js, as I&#039;ve found object/member detection has proven adequate.</description>
		<content:encoded><![CDATA[<p>I definitely prefer conditional comments to use of css hacks.  Similar to the method Phil linked to on PIE, I&#8217;ve recently taken to using a single conditional comment block wrapping the open body tag, assigning a class=&#8221;IE [IE ver]&#8220;.  This allows me to use the cascade to override style rules in a single style sheet as needed per whichever version of IE is creating mayhem in whatever fashion.</p>
<p>I haven&#8217;t used conditional comments in js, as I&#8217;ve found object/member detection has proven adequate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil</title>
		<link>http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/#comment-1394</link>
		<dc:creator>Phil</dc:creator>
		<pubDate>Mon, 23 Jul 2007 23:37:13 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/#comment-1394</guid>
		<description>&lt;a href=&quot;http://www.unintentionallyblank.co.uk/2006/08/14/if-internet-explorer-then-do-something-else/&quot; rel=&quot;nofollow&quot;&gt;I am a big fan of conditional comments&lt;/a&gt;, I see them as a clean and safe way to do the dirty work for IE and I much prefer them to hacks.

I don&#039;t think their use should be entirely restricted to the &lt;head&gt; of a document, I use them to advertise Firefox to IE users only and Calvin&#039;s example above makes sense too.

However I came across &lt;a href=&quot;http://positioniseverything.net/articles/cc-plus.html&quot; rel=&quot;nofollow&quot;&gt;this article on Position Is Everything&lt;/a&gt; the other day and felt that it was too much. Sure, we could add extra markup to the page, but as you say, that is just changing the problem, albeit in a way that makes it easier to fix in some respects. But extra markup and another hack to target non IE browsers seemed too much.

I guess it is down to a matter of taste in the end, but I mostly agree with you, Jon.</description>
		<content:encoded><![CDATA[<p><a href="http://www.unintentionallyblank.co.uk/2006/08/14/if-internet-explorer-then-do-something-else/" rel="nofollow">I am a big fan of conditional comments</a>, I see them as a clean and safe way to do the dirty work for IE and I much prefer them to hacks.</p>
<p>I don&#8217;t think their use should be entirely restricted to the &lt;head&gt; of a document, I use them to advertise Firefox to IE users only and Calvin&#8217;s example above makes sense too.</p>
<p>However I came across <a href="http://positioniseverything.net/articles/cc-plus.html" rel="nofollow">this article on Position Is Everything</a> the other day and felt that it was too much. Sure, we could add extra markup to the page, but as you say, that is just changing the problem, albeit in a way that makes it easier to fix in some respects. But extra markup and another hack to target non IE browsers seemed too much.</p>
<p>I guess it is down to a matter of taste in the end, but I mostly agree with you, Jon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Calvin</title>
		<link>http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/#comment-1395</link>
		<dc:creator>Calvin</dc:creator>
		<pubDate>Mon, 23 Jul 2007 19:37:05 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/#comment-1395</guid>
		<description>At work the Marketing department wanted a button on the homepage, as well as final page of the order process that allowed people to make our website their homepage.

With only IE supporting the JavaScript that provides this functionality, it didn&#039;t really seem right to have the button displayed to all users. Conditional comments to the rescue! By far the quickest and easiest way to make sure that the &quot;Make homepage&quot; button is displayed to IE only users.</description>
		<content:encoded><![CDATA[<p>At work the Marketing department wanted a button on the homepage, as well as final page of the order process that allowed people to make our website their homepage.</p>
<p>With only IE supporting the JavaScript that provides this functionality, it didn&#8217;t really seem right to have the button displayed to all users. Conditional comments to the rescue! By far the quickest and easiest way to make sure that the &#8220;Make homepage&#8221; button is displayed to IE only users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/#comment-1390</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Mon, 23 Jul 2007 14:41:37 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2007/07/23/taking-conditional-comments-too-far/#comment-1390</guid>
		<description>@Alexander Gyoshev: Yes, Stu Nicholls was one of the first that came to mind when writing this article.  In my opinion, while his examples are innovative for sure, they would be better suited to use JavaScript where acceptable.  Using conditional comments in that way is using structural markup to affect the behavior of the document -- something for which JavaScript is better suited.  What do you think?

Going beyond JavaScript-less CSS techniques, I came across conditional comments being used in the &lt;code&gt;body&lt;/code&gt; of &lt;a href=&quot;http://nytimes.com&quot; rel=&quot;nofollow&quot;&gt;http://nytimes.com&lt;/a&gt; not too long ago.  Unfortunately, the snippet has been removed, but that too was also inspiration for the article.</description>
		<content:encoded><![CDATA[<p>@Alexander Gyoshev: Yes, Stu Nicholls was one of the first that came to mind when writing this article.  In my opinion, while his examples are innovative for sure, they would be better suited to use JavaScript where acceptable.  Using conditional comments in that way is using structural markup to affect the behavior of the document &#8212; something for which JavaScript is better suited.  What do you think?</p>
<p>Going beyond JavaScript-less CSS techniques, I came across conditional comments being used in the <code>body</code> of <a href="http://nytimes.com" rel="nofollow">http://nytimes.com</a> not too long ago.  Unfortunately, the snippet has been removed, but that too was also inspiration for the article.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using xcache (user agent is rejected)
Database Caching using xcache

Served from: mondaybynoon.com @ 2010-07-30 22:02:29 -->