<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Scarf*oo &#187; IE</title>
	<atom:link href="http://scarfoo.com/archives/category/web-development/ie/feed" rel="self" type="application/rss+xml" />
	<link>http://scarfoo.com</link>
	<description>Comfy Web Development With Standards in Mind</description>
	<lastBuildDate>Wed, 19 May 2010 18:59:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>CSS Differences in Internet Explorer 6, 7 and 8 «  Smashing Magazine</title>
		<link>http://scarfoo.com/archives/259</link>
		<comments>http://scarfoo.com/archives/259#comments</comments>
		<pubDate>Wed, 14 Oct 2009 16:32:53 +0000</pubDate>
		<dc:creator>Damjan Mozetič</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[IE]]></category>
		<category><![CDATA[news]]></category>

		<guid isPermaLink="false">http://scarfoo.com/?p=259</guid>
		<description><![CDATA[If you haven&#8217;t decided to drop IE6 support, this might be the right time to do it. The article CSS Differences in Internet Explorer 6, 7 and 8 over at Smashing Magazine is a great reference to CSS differences between various IE versions when handling advanced CSS rules. Looks like versions 7 and up already [...]]]></description>
			<content:encoded><![CDATA[<p>If you haven&#8217;t decided to drop IE6 support, this might be the right time to do it. The article <a href='http://www.smashingmagazine.com/2009/10/14/css-differences-in-internet-explorer-6-7-and-8/'>CSS Differences in Internet Explorer 6, 7 and 8</a> over at Smashing Magazine is a great reference to CSS differences between various IE versions when handling advanced CSS rules. Looks like versions 7 and up already support the vast majority of rules you throw at them, so if you want to take advantage of advanced CSS selectors to ease styles development, go on, I don&#8217;t believe many will be hurt in the process.</p>
<div id="crp_related"><h3>Related Posts:</h3><ul><li><a href="http://scarfoo.com/archives/235" rel="bookmark" class="crp_title">Universal Internet Explorer 6 CSS</a></li><li><a href="http://scarfoo.com/archives/50" rel="bookmark" class="crp_title">CSS Gradients Support in WebKit</a></li><li><a href="http://scarfoo.com/archives/30" rel="bookmark" class="crp_title">Browser Version Targeting Anyone?</a></li><li>Powered by <a href="http://ajaydsouza.com/wordpress/plugins/contextual-related-posts/">Contextual Related Posts</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>http://scarfoo.com/archives/259/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Universal Internet Explorer 6 CSS</title>
		<link>http://scarfoo.com/archives/235</link>
		<comments>http://scarfoo.com/archives/235#comments</comments>
		<pubDate>Thu, 21 May 2009 11:08:33 +0000</pubDate>
		<dc:creator>Damjan Mozetič</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[IE]]></category>
		<category><![CDATA[news]]></category>
		<category><![CDATA[IE6]]></category>
		<category><![CDATA[readable]]></category>
		<category><![CDATA[universal CSS]]></category>

		<guid isPermaLink="false">http://scarfoo.com/?p=235</guid>
		<description><![CDATA[Too bad that there are still many clients running and demanding your product to run on IE6. At least in my case, 80% of the clients are of the aforementioned sort and I am in no position to change that. It&#8217;s a sad sad thing really. Someone should really write a conditionally included universal CSS [...]]]></description>
			<content:encoded><![CDATA[<p>Too bad that there are still many clients running and demanding your product to run on IE6. At least in my case, 80% of the clients are of the aforementioned sort and I am in no position to change that. It&#8217;s a sad sad thing really.</p>
<p>Someone should really write a conditionally included universal CSS file to handle IE6 bugs and just be off with it. On the other hand, there are other approaches such as providing a universal readable and pleasant style just for IE6 users and hoping the clients will be happy with it.</p>
<p>Check the proposed style in question at <a href='http://forabeautifulweb.com/blog/about/universal_internet_explorer_6_css/'>Universal Internet Explorer 6 CSS | For A Beautiful Web</a>.</p>
<div id="crp_related"><h3>Related Posts:</h3><ul><li><a href="http://scarfoo.com/archives/11" rel="bookmark" class="crp_title">CSS Tip #1 &#8211; Avoiding Hacks With IE Conditional Comments</a></li><li><a href="http://scarfoo.com/archives/259" rel="bookmark" class="crp_title">CSS Differences in Internet Explorer 6, 7 and 8 «  Smashing Magazine</a></li><li><a href="http://scarfoo.com/archives/270" rel="bookmark" class="crp_title">A Sad Day For Rock And Roll.</a></li><li>Powered by <a href="http://ajaydsouza.com/wordpress/plugins/contextual-related-posts/">Contextual Related Posts</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>http://scarfoo.com/archives/235/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Oh No! More Internet Explorers.</title>
		<link>http://scarfoo.com/archives/174</link>
		<comments>http://scarfoo.com/archives/174#comments</comments>
		<pubDate>Fri, 20 Mar 2009 14:15:12 +0000</pubDate>
		<dc:creator>Damjan Mozetič</dc:creator>
				<category><![CDATA[IE]]></category>
		<category><![CDATA[news]]></category>
		<category><![CDATA[IE8]]></category>

		<guid isPermaLink="false">http://scarfoo.com/?p=174</guid>
		<description><![CDATA[While I loved playing Lemmings, I never loved playing with IE. After spending a full week in bed, this is the first news I ended up stumbling into &#8211; IE8 Has Arrived. My head is still swimming around from the fever, so you&#8217;ll excuse me for not delving into the depths of this release. Related [...]]]></description>
			<content:encoded><![CDATA[<p>While I loved playing Lemmings, I never loved playing with IE. After spending a full week in bed, this is the first news I ended up stumbling into &#8211; <a href='http://www.webstandards.org/2009/03/20/ie8-has-arrived/'>IE8 Has Arrived</a>. My head is still swimming around from the fever, so you&#8217;ll excuse me for not delving into the depths of this release.</p>
<div id="crp_related"><h3>Related Posts:</h3><ul><li><a href="http://scarfoo.com/archives/39" rel="bookmark" class="crp_title">Microsoft&#8217;s Interoperability Principles and IE8</a></li><li><a href="http://scarfoo.com/archives/18" rel="bookmark" class="crp_title">Hell froze over. IE8 passes ACID2 test!</a></li><li><a href="http://scarfoo.com/archives/233" rel="bookmark" class="crp_title">Interview with Ian Hickson, editor of the HTML 5 specification. &#8211; The Web Standards Project</a></li><li>Powered by <a href="http://ajaydsouza.com/wordpress/plugins/contextual-related-posts/">Contextual Related Posts</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>http://scarfoo.com/archives/174/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The Solution to Your IE PNG Background Problems</title>
		<link>http://scarfoo.com/archives/111</link>
		<comments>http://scarfoo.com/archives/111#comments</comments>
		<pubDate>Tue, 09 Dec 2008 07:22:53 +0000</pubDate>
		<dc:creator>Damjan Mozetič</dc:creator>
				<category><![CDATA[IE]]></category>
		<category><![CDATA[news]]></category>
		<category><![CDATA[background images]]></category>
		<category><![CDATA[DD_belatedPNG]]></category>
		<category><![CDATA[PNG]]></category>

		<guid isPermaLink="false">http://scarfoo.com/?p=111</guid>
		<description><![CDATA[Ever happened to you that after applying one of the many solutions for fixing IE&#8217;s png background image support, links on that element didn&#8217;t work? How about repeating background images? I bet most of you will nod in agreement. Well, Drew Diller from dillerdesign.com&#8216;s got the solution for you. While his script fails to apply [...]]]></description>
			<content:encoded><![CDATA[<p>Ever happened to you that after applying one of the many solutions for fixing IE&#8217;s png background image support, links on that element didn&#8217;t work? How about repeating background images? I bet most of you will nod in agreement. Well, Drew Diller from <a href="http://www.dillerdesign.com">dillerdesign.com</a>&#8216;s got the solution for you. While his script fails to apply PNGs to the body element and to an img tag (for now), it solves the problem with background-position and background-repeat.</p>
<p>All you have to do is call the following script and voila, your headaches are over:</p>
<pre>
<code>&lt;!--[if IE 6]&gt;
&lt;script src="DD_belatedPNG.js"&gt;&lt;/script&gt;
&lt;script&gt;
    DD_belatedPNG.fix('.png_bg'); //EXAMPLE
&lt;/script&gt;
&lt;![endif]--&gt;</code>
</pre>
<p>Head over to the <a href="http://www.dillerdesign.com/experiment/DD_belatedPNG/">DD_belatedPNG page</a> for downloads and more examples.</p>
<div id="crp_related"><h3>Related Posts:</h3><ul><li><a href="http://scarfoo.com/archives/16" rel="bookmark" class="crp_title">5 CSS Tips to Make IE (You) Happy</a></li><li><a href="http://scarfoo.com/archives/218" rel="bookmark" class="crp_title">What are web standards?</a></li><li><a href="http://scarfoo.com/archives/212" rel="bookmark" class="crp_title">The Shorthand CSS Notation Explained &#8211; Back to The Basics</a></li><li>Powered by <a href="http://ajaydsouza.com/wordpress/plugins/contextual-related-posts/">Contextual Related Posts</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>http://scarfoo.com/archives/111/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>RNIB Surf Right Toolbar</title>
		<link>http://scarfoo.com/archives/63</link>
		<comments>http://scarfoo.com/archives/63#comments</comments>
		<pubDate>Sun, 22 Jun 2008 10:33:09 +0000</pubDate>
		<dc:creator>Damjan Mozetič</dc:creator>
				<category><![CDATA[IE]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[news]]></category>
		<category><![CDATA[software]]></category>

		<guid isPermaLink="false">http://scarfoo.com/?p=63</guid>
		<description><![CDATA[The People at RNIB have released the Surf Right Toolbar, which is &#8212; you guessed it &#8212; a toolbar for IE, which is designed to bring to the surface the often hidden accessibilty settings, such as turning javascript and images on/off, changing text size and so on. Quoting: &#8220;The Surf Right Toolbar is really for [...]]]></description>
			<content:encoded><![CDATA[<p>The People at <a href="http://www.rnib.org.uk/">RNIB</a> have released the <a href="http://www.rnib.org.uk/wacblog/news/rnib-surf-right-toolbar-beta-version-available">Surf Right Toolbar</a>, which is &#8212; you guessed it &#8212; a toolbar for IE, which is designed to bring to the surface the often hidden accessibilty settings, such as turning javascript and images on/off, changing text size and so on.</p>
<p>Quoting:<br />
&#8220;The Surf Right Toolbar is really for anyone who wants to adjust the way they view content on the web to make it easier to read. This could include people with mild disabilities, the elderly, people with reading problems, cognitive problems, using dial-up, photosensitivity and so on.&#8221;</p>
<p><img src='http://www.rnib.org.uk/wacblog/wp-content/uploads/2008/06/toolbar2.jpg' alt='The Surf Right Toolbar' class='alignnone' /></p>
<p>You can <a href="http://www.rnib.org.uk/wacblog/news/rnib-surf-right-toolbar-beta-version-available">grab the beta, right here</a>.</p>
<div id="crp_related"><h3>Related Posts:</h3><ul><li><a href="http://scarfoo.com/archives/138" rel="bookmark" class="crp_title">Safari 4 Public Beta</a></li><li><a href="http://scarfoo.com/archives/69" rel="bookmark" class="crp_title">ALA &#8211; The Survey For People Who Make Websites 2008</a></li><li><a href="http://scarfoo.com/archives/263" rel="bookmark" class="crp_title">&#8220;It&#8217;s like twitter. Except we charge people to use it.&#8221;</a></li><li>Powered by <a href="http://ajaydsouza.com/wordpress/plugins/contextual-related-posts/">Contextual Related Posts</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>http://scarfoo.com/archives/63/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Microsoft&#8217;s Interoperability Principles and IE8</title>
		<link>http://scarfoo.com/archives/39</link>
		<comments>http://scarfoo.com/archives/39#comments</comments>
		<pubDate>Tue, 04 Mar 2008 08:11:30 +0000</pubDate>
		<dc:creator>Damjan Mozetič</dc:creator>
				<category><![CDATA[IE]]></category>
		<category><![CDATA[standards]]></category>
		<category><![CDATA[web development]]></category>
		<category><![CDATA[Dean Hachnamovitch]]></category>
		<category><![CDATA[IE8]]></category>

		<guid isPermaLink="false">http://scarfoo.com/archives/39</guid>
		<description><![CDATA[&#8220;We’ve decided that IE8 will, by default, interpret web content in the most standards compliant way it can. This decision is a change from what we’ve posted previously.&#8221; &#8211; Dean Hachamovitch, General Manager Internet Explorer So the flames have extinguished? Read more on the subject. Related Posts:Hell froze over. IE8 passes ACID2 test!Oh No! More [...]]]></description>
			<content:encoded><![CDATA[<p>&#8220;We’ve decided that IE8 will, by default, interpret web content in the most standards compliant way it can. This decision is a change from what we’ve posted previously.&#8221;<br />
<em>&#8211; Dean Hachamovitch, General Manager Internet Explorer</em></p>
<p>So <a href="http://scarfoo.com/archives/30">the flames</a> have extinguished? <a href="http://blogs.msdn.com/ie/archive/2008/03/03/microsoft-s-interoperability-principles-and-ie8.aspx">Read more</a> on the subject.</p>
<div id="crp_related"><h3>Related Posts:</h3><ul><li><a href="http://scarfoo.com/archives/18" rel="bookmark" class="crp_title">Hell froze over. IE8 passes ACID2 test!</a></li><li><a href="http://scarfoo.com/archives/174" rel="bookmark" class="crp_title">Oh No! More Internet Explorers.</a></li><li><a href="http://scarfoo.com/archives/23" rel="bookmark" class="crp_title">NewsGator Releases NetNewsWire For Free</a></li><li>Powered by <a href="http://ajaydsouza.com/wordpress/plugins/contextual-related-posts/">Contextual Related Posts</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>http://scarfoo.com/archives/39/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Browser Version Targeting Anyone?</title>
		<link>http://scarfoo.com/archives/30</link>
		<comments>http://scarfoo.com/archives/30#comments</comments>
		<pubDate>Tue, 22 Jan 2008 08:13:52 +0000</pubDate>
		<dc:creator>Damjan Mozetič</dc:creator>
				<category><![CDATA[IE]]></category>
		<category><![CDATA[standards]]></category>
		<category><![CDATA[web development]]></category>
		<category><![CDATA[browser version targeting]]></category>
		<category><![CDATA[doctype]]></category>
		<category><![CDATA[edge]]></category>
		<category><![CDATA[forward compatibility]]></category>
		<category><![CDATA[hasLayout]]></category>
		<category><![CDATA[IE8]]></category>
		<category><![CDATA[meta]]></category>
		<category><![CDATA[version targeting]]></category>
		<category><![CDATA[web standards]]></category>

		<guid isPermaLink="false">http://scarfoo.com/archives/30</guid>
		<description><![CDATA[Sooner than later we may be dropped into a world of version targeting and forward compatibility, when it comes to web development. The basic idea is to use a meta declaration to specify which browsers and versions our web page intends to support. For example, writing: &#60;meta http-equiv="X-UA-Compatible" content="IE=7;FF=2" /&#62; &#8230; would say that our [...]]]></description>
			<content:encoded><![CDATA[<p>Sooner than later we may be dropped into a world of version targeting and forward compatibility, when it comes to web development. The basic idea is to use a meta declaration to specify which browsers and versions our web page intends to support. For example, writing:</p>
<pre>
<code>&lt;meta http-equiv="X-UA-Compatible" content="IE=7;FF=2" /&gt;</code>
</pre>
<p>&#8230; would say that our page was tested and works on <abbr>IE</abbr> version 7 and Firefox version 2, for example.</p>
<p>Now, the problem I see here is in actual browser support for backwards-compatibility rendering. Do we really believe that once <abbr>IE</abbr> 10 is out, our IE=7 will still work? If you ask me, this is a recipe for failure. </p>
<p>Read more on the subject on <a href="http://www.alistapart.com">alistapart.com</a>, for some <a href="http://alistapart.com/articles/beyonddoctype">enlightening</a> <a href="http://alistapart.com/articles/fromswitchestotargets">articles</a> on the subject.</p>
<div id="crp_related"><h3>Related Posts:</h3><ul><li><a href="http://scarfoo.com/archives/11" rel="bookmark" class="crp_title">CSS Tip #1 &#8211; Avoiding Hacks With IE Conditional Comments</a></li><li><a href="http://scarfoo.com/archives/50" rel="bookmark" class="crp_title">CSS Gradients Support in WebKit</a></li><li><a href="http://scarfoo.com/archives/40" rel="bookmark" class="crp_title">Safari 3.1 Update Released</a></li><li>Powered by <a href="http://ajaydsouza.com/wordpress/plugins/contextual-related-posts/">Contextual Related Posts</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>http://scarfoo.com/archives/30/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>5 CSS Tips to Make IE (You) Happy</title>
		<link>http://scarfoo.com/archives/16</link>
		<comments>http://scarfoo.com/archives/16#comments</comments>
		<pubDate>Tue, 25 Dec 2007 20:16:06 +0000</pubDate>
		<dc:creator>Damjan Mozetič</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[IE]]></category>
		<category><![CDATA[web development]]></category>
		<category><![CDATA[double margin]]></category>
		<category><![CDATA[has layout]]></category>
		<category><![CDATA[hover]]></category>
		<category><![CDATA[htc]]></category>
		<category><![CDATA[mouseover]]></category>
		<category><![CDATA[png support]]></category>
		<category><![CDATA[pngfix]]></category>
		<category><![CDATA[reset browser styles]]></category>
		<category><![CDATA[tips]]></category>
		<category><![CDATA[translucency]]></category>
		<category><![CDATA[transparency]]></category>

		<guid isPermaLink="false">http://scarfoo.com/archives/16</guid>
		<description><![CDATA[If I could, I&#8217;d give you a special present this christmas &#8211; I&#8217;d tell you how to make IE on Windows behave like a grown-up browser. Sadly, reality sucks &#8211; as does IE on Windows &#8211; so I can only offer to share with you a couple of CSS tips to ease the pain of [...]]]></description>
			<content:encoded><![CDATA[<p>If I could, I&#8217;d give you a special present this christmas &#8211; I&#8217;d tell you how to make IE on Windows behave like a grown-up browser. Sadly, reality sucks &#8211; as does IE on Windows &#8211;  so I can only offer to share with you a couple of CSS tips to ease the pain of working with that piece of crappy software.<br />
<span id="more-16"></span></p>
<h3>1. Reset browser styles</h3>
<p>To start off with the right leg, I suggest you reset the styles to some sensitive defaults, so all browsers will render the page as similarly as possible. To do so, you can use one of the <a href="http://www.ejeliot.com/blog/85">many</a> <a href="http://developer.yahoo.com/yui/reset/">suggested</a> <a href="http://meyerweb.com/eric/thoughts/2008/01/15/resetting-again/">templates</a> to create a reset.css file and include it before you include any other of your style sheets.</p>
<h3>2. Add IE 5.5+ png file support</h3>
<p>Angus Turnbull over at <a href="http://www.twinhelix.com/">TwinHelix</a> has written a nice <a href="http://www.twinhelix.com/css/iepngfix/">htc script</a> to bring png images support to IE 5.5+. To use it, simply add the following css code into your ie.css file, which you&#8217;ve previously included with <a href="http://scarfoo.com/archives/11">IE conditional comments</a> &#8211; you <strong>do</strong> use conditional comments, right?</p>
<pre>
<code>img, h1, .class-with-png-background-image {
    behavior: url(../htc/iepngfix.htc);
}</code>
</pre>
<p>I won&#8217;t go deep into explaining how this works as you can easily find more info on the <a href="http://www.twinhelix.com/css/iepngfix/">author&#8217;s site</a>. Suffice to say that you need to call the iepngfix.htc file as an ie-only <a href="http://msdn2.microsoft.com/en-us/library/ms531079(VS.85).aspx">dhtml behaviour</a> attribute on the img element and/or any other element where you may want to use png background images on.<br />
The only problem with this script that I&#8217;ve found so far, is that it won&#8217;t work with repeating background images.<br />
Also you should make sure that the server is configured to serve .htc files correctly. If the script doesn&#8217;t work, all you need to do is to add the following line to your .htaccess file, and you should be good to go:</p>
<pre>
<code>AddType text/x-component .htc</code>
</pre>
<h3>3. Add IE &lt; 7 custom :hover support</h3>
<p>Another annoying IE problem is that it doesn&#8217;t support css :hover events on elements other than links. This can be easily solved with another .htc script, this time written by <a href="http://www.xs4all.nl/~peterned/">Peter Nederlof</a> and you can download it on the <a href="http://www.xs4all.nl/~peterned/csshover.html">Whatever:hover script page</a>.<br />
This script is even easier to use than the png trick, because all it takes is one line in your ie-specific css file:</p>
<pre>
<code>body { behavior:url("../htc/csshover.htc"); }</code>
</pre>
<h3>4. &#8220;Give layout&#8221; to elements</h3>
<p>The source of most of Internet Explorer&#8217;s bugs comes from an IE-only property called <em>layout</em>. An element can either have layout or not, which determines how an element is rendered by the browser. Most of IE bugs can be squashed by giving layout to the offending element, which is done simply by assigning one of the following properties to that element:</p>
<p>position: absolute [IE 6 &#038; 7]<br />
float: left [IE 6 &#038; 7]<br />
float: right [IE 6 &#038; 7]<br />
display: inline-table [IE 6 &#038; 7]<br />
any width or height value [IE 6 &#038; 7]<br />
zoom [IE 6 &#038; 7]<br />
min-width [IE 7]<br />
max-width [IE 7]<br />
min-height [IE 7]<br />
max-height [IE 7]<br />
overflow [IE 7]</p>
<p>Among these, the most common way to &#8220;give layout&#8221; to an element &#8211; and thus, eliminate the bug &#8211; is to assign the following rule:</p>
<pre>
<code>#the-buggy-element { height: 1%; }</code>
</pre>
<p>However, if the problem persists, you might want to add a &#8220;position&#8221; to that element. This fixes the problem more often than not.</p>
<pre>
<code>#the-buggy-element {
    position: relative;
    height: 1%;
}</code>
</pre>
<p>An exhaustive article on <em>having layout</em> can be found at <a href="http://www.satzansatz.de/cssd/onhavinglayout.html">http://www.satzansatz.de/cssd/onhavinglayout.html</a>.</p>
<h3>5. Prevent the double margin bug from crumbling your layout</h3>
<p>This one has saved me a lot of headaches, because IE 6 has a tendency to <strong>double</strong> the margins of every element, which has been floated <strong>and</strong> assigned a left/right margin. To overcome this bug, simply set <em>display: inline</em> on the offending element. This will magically make the bug disappear with no adverse effects on your layout.</p>
<p>If you&#8217;ve found these tips useful and your future IE-development experience somewhat more pleasant, I invite you to share your thoughts by commenting below.</p>
<div id="crp_related"><h3>Related Posts:</h3><ul><li><a href="http://scarfoo.com/archives/111" rel="bookmark" class="crp_title">The Solution to Your IE PNG Background Problems</a></li><li><a href="http://scarfoo.com/archives/11" rel="bookmark" class="crp_title">CSS Tip #1 &#8211; Avoiding Hacks With IE Conditional Comments</a></li><li><a href="http://scarfoo.com/archives/38" rel="bookmark" class="crp_title">Development Diary: 4 Tips on Working With Fluid Layouts</a></li><li>Powered by <a href="http://ajaydsouza.com/wordpress/plugins/contextual-related-posts/">Contextual Related Posts</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>http://scarfoo.com/archives/16/feed</wfw:commentRss>
		<slash:comments>27</slash:comments>
		</item>
		<item>
		<title>Hell froze over. IE8 passes ACID2 test!</title>
		<link>http://scarfoo.com/archives/18</link>
		<comments>http://scarfoo.com/archives/18#comments</comments>
		<pubDate>Thu, 20 Dec 2007 07:43:24 +0000</pubDate>
		<dc:creator>Damjan Mozetič</dc:creator>
				<category><![CDATA[IE]]></category>
		<category><![CDATA[web development]]></category>
		<category><![CDATA[ACID]]></category>
		<category><![CDATA[ACID 2]]></category>
		<category><![CDATA[ACID2]]></category>
		<category><![CDATA[IE8]]></category>
		<category><![CDATA[internet explorer]]></category>

		<guid isPermaLink="false">http://scarfoo.com/archives/18</guid>
		<description><![CDATA[I believe I owe some people a beer or two now that hell actually froze over. Believe it or not, but the current milestone of internet explorer 8 passes the unforgivable ACID2 test with full votes! Related Posts:WebKit achieves Acid3 100/100 in public buildMicrosoft&#8217;s Interoperability Principles and IE8Oh No! More Internet Explorers.Powered by Contextual Related [...]]]></description>
			<content:encoded><![CDATA[<p>I believe I owe some people a beer or two now that hell actually froze over. Believe it or not, but the current milestone of <a href="http://blogs.msdn.com/ie/archive/2007/12/19/internet-explorer-8-and-acid2-a-milestone.aspx">internet explorer 8 passes</a> the unforgivable <a href="http://www.webstandards.org/files/acid2/test.html">ACID2 test</a> with full votes!</p>
<div id="crp_related"><h3>Related Posts:</h3><ul><li><a href="http://scarfoo.com/archives/42" rel="bookmark" class="crp_title">WebKit achieves Acid3 100/100 in public build</a></li><li><a href="http://scarfoo.com/archives/39" rel="bookmark" class="crp_title">Microsoft&#8217;s Interoperability Principles and IE8</a></li><li><a href="http://scarfoo.com/archives/174" rel="bookmark" class="crp_title">Oh No! More Internet Explorers.</a></li><li>Powered by <a href="http://ajaydsouza.com/wordpress/plugins/contextual-related-posts/">Contextual Related Posts</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>http://scarfoo.com/archives/18/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>CSS Tip #1 &#8211; Avoiding Hacks With IE Conditional Comments</title>
		<link>http://scarfoo.com/archives/11</link>
		<comments>http://scarfoo.com/archives/11#comments</comments>
		<pubDate>Thu, 06 Dec 2007 21:09:34 +0000</pubDate>
		<dc:creator>Damjan Mozetič</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[IE]]></category>
		<category><![CDATA[web development]]></category>
		<category><![CDATA[bugs]]></category>
		<category><![CDATA[conditional comments]]></category>
		<category><![CDATA[hacks]]></category>

		<guid isPermaLink="false">http://scarfoo.com/?p=11</guid>
		<description><![CDATA[I am pretty sure that every web designer found himself stuck with one or more of Internet Explorer&#8217;s annoying bugs and usually he ended up using css hacks to isolate the problem(s). Well, I believe hacks should be used with caution, if used at all, since you never know what adverse effects it may have [...]]]></description>
			<content:encoded><![CDATA[<p>I am pretty sure that every web designer found himself stuck with one or more of Internet Explorer&#8217;s annoying bugs and usually he ended up using <a href="http://en.wikipedia.org/wiki/CSS_hack">css hacks</a> to isolate the problem(s). Well, I believe hacks should be used with caution, if used at all, since you never know what adverse effects it may have on your web site with future browser updates.</p>
<p>Fortunately IE developers provided us with a neat solution to this problem with <strong>conditional comments</strong>. Just what are conditional comments? Basically they are common html comments with an extended syntax. They are completely transparent to all non-IE browsers, so they <strong>validate</strong> and are much more future-proof than hacks will ever be.</p>
<p><span id="more-11"></span></p>
<p>You can use conditional comments like this:</p>
<pre>
<code>&lt;!--[if IE 6]&gt;
&lt;link type="text/css" href="ie6.css" rel="stylesheet"&gt;
&lt;![endif]--&gt;</code>
</pre>
<p>or like this:</p>
<pre>
<code>&lt;!--[if IE 6]&gt;
&lt;style type="text/css"&gt;
... css definitions ...
&lt;/style&gt;
&lt;![endif]--&gt;</code>
</pre>
<p>In both cases the styles will only be used from Internet Explorer version 6. Of course we can specify any version of IE we want, like this:</p>
<pre>
<code>&lt;!--[if lt IE 7]&gt;
... will only run on ie less than version 7 ...
&lt;![endif]--&gt;

&lt;!--[if lte IE 7]&gt;
... will run on ie less than or equal to version 7 ...
&lt;![endif]--&gt;

&lt;!--[if gte IE 7]&gt;
... will run on every ie greater or equal to version 7 ...
&lt;![endif]--&gt;</code>
</pre>
<p>&#8230; and on and on, I am sure you figured out how it works. Still, if you want more info on the subject, you can get it from the <a href="http://msdn2.microsoft.com/en-us/library/ms537512.aspx">MSDN pages in the IE Developer Center</a>.</p>
<p>Have fun!</p>
<div id="crp_related"><h3>Related Posts:</h3><ul><li><a href="http://scarfoo.com/archives/16" rel="bookmark" class="crp_title">5 CSS Tips to Make IE (You) Happy</a></li><li><a href="http://scarfoo.com/archives/30" rel="bookmark" class="crp_title">Browser Version Targeting Anyone?</a></li><li><a href="http://scarfoo.com/archives/111" rel="bookmark" class="crp_title">The Solution to Your IE PNG Background Problems</a></li><li>Powered by <a href="http://ajaydsouza.com/wordpress/plugins/contextual-related-posts/">Contextual Related Posts</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>http://scarfoo.com/archives/11/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
