<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: One Year Ago &#124; CSS Hacks</title>
	<link>http://fadtastic.net/2006/10/01/one-year-ago-css-hacks/</link>
	<description>thoughts on &#124; comments about &#124; examples of  } web design trends.</description>
	<pubDate>Fri, 08 Aug 2008 21:23:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>By: Nate K</title>
		<link>http://fadtastic.net/2006/10/01/one-year-ago-css-hacks/#comment-4832</link>
		<author>Nate K</author>
		<pubDate>Sun, 01 Oct 2006 14:10:47 +0000</pubDate>
		<guid>http://fadtastic.net/2006/10/01/one-year-ago-css-hacks/#comment-4832</guid>
					<description>Personally, I haven't used them for quite some time now. The last time I used them was on a project built by someone else - for a corporate site that used a box model hack. 

I don't like them - and don't plan on using them. I will find other ways to get the job done (that will be semantically correct and valid).

IF hacks HAVE to be used - at least manage them separately in order for easy fixes or upgrades when the browsers change.</description>
		<content:encoded><![CDATA[<p>Personally, I haven&#8217;t used them for quite some time now. The last time I used them was on a project built by someone else - for a corporate site that used a box model hack. </p>
<p>I don&#8217;t like them - and don&#8217;t plan on using them. I will find other ways to get the job done (that will be semantically correct and valid).</p>
<p>IF hacks HAVE to be used - at least manage them separately in order for easy fixes or upgrades when the browsers change.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Andrew Faulkner</title>
		<link>http://fadtastic.net/2006/10/01/one-year-ago-css-hacks/#comment-4834</link>
		<author>Andrew Faulkner</author>
		<pubDate>Sun, 01 Oct 2006 14:23:54 +0000</pubDate>
		<guid>http://fadtastic.net/2006/10/01/one-year-ago-css-hacks/#comment-4834</guid>
					<description>&lt;blockquote&gt;IF hacks HAVE to be used - at least manage them separately in order for easy fixes or upgrades when the browsers change.&lt;/blockquote&gt;

An excellent suggestion, Nate. Do you mean by using a seperate stylesheet?</description>
		<content:encoded><![CDATA[<blockquote><p>IF hacks HAVE to be used - at least manage them separately in order for easy fixes or upgrades when the browsers change.</p>
</blockquote>
<p>An excellent suggestion, Nate. Do you mean by using a seperate stylesheet?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: gareth</title>
		<link>http://fadtastic.net/2006/10/01/one-year-ago-css-hacks/#comment-4837</link>
		<author>gareth</author>
		<pubDate>Sun, 01 Oct 2006 16:02:12 +0000</pubDate>
		<guid>http://fadtastic.net/2006/10/01/one-year-ago-css-hacks/#comment-4837</guid>
					<description>I find that i very rarely have to use css hacks.. what are people doing to have to use them? on the very odd occasion, when deadlines are tight I use conditional comments.</description>
		<content:encoded><![CDATA[<p>I find that i very rarely have to use css hacks.. what are people doing to have to use them? on the very odd occasion, when deadlines are tight I use conditional comments.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Johan</title>
		<link>http://fadtastic.net/2006/10/01/one-year-ago-css-hacks/#comment-4843</link>
		<author>Johan</author>
		<pubDate>Sun, 01 Oct 2006 18:08:59 +0000</pubDate>
		<guid>http://fadtastic.net/2006/10/01/one-year-ago-css-hacks/#comment-4843</guid>
					<description>You can use either IE conditional comments to serve certain CSS rules to target a specifc IE WIn version (IE5+). Though many designers and coders dont use them often unless to add the &lt;a href="http://www.satzansatz.de/cssd/onhavinglayout.html" rel="nofollow"&gt;hasLayout&lt;/a&gt;
property (in  short when an element has no dimensions set like width, height you get trouble as in CSS bugs).

IE and hacks

Star html Selector Bug for IE7-

Some examples
&lt;a href="http://www.quirksmode.org/css/csshacks.html" rel="nofollow"&gt;css hacks&lt;/a&gt;

eg * html #container{

}

Other &lt;a href="http://brunildo.org/test/csshacks.html" rel="nofollow"&gt;hacks&lt;/a&gt; which could be used and are considered save. Though are rarely used.

Advice: avoid hacks at all costs that rely on parser bugs in browsers. 

Some advanced CSS3 selectors which are not understood by ALL browsers can be used to target a specific browsers eg IE7 or Opera and filter out others. These hacks do NOT rely on  parser bugs in browsers but are at the same time not really handy (not easy to remember)  and maybe not future proof. Eventually other browsers could catch up and  be able to read them too.

Examples

&lt;a href="http://www.brothercake.com/site/resources/reference/xxx/" rel="nofollow"&gt;IE7&lt;/a&gt;
For Opera (CSS queries:
Eg &lt;a href="http://www.fu2k.org/alex/css/hacks/fuzzyspecificity#op8andup" rel="nofollow"&gt;@media all and (min-width: 0px)&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>You can use either IE conditional comments to serve certain CSS rules to target a specifc IE WIn version (IE5+). Though many designers and coders dont use them often unless to add the <a href="http://www.satzansatz.de/cssd/onhavinglayout.html" rel="nofollow">hasLayout</a><br />
property (in  short when an element has no dimensions set like width, height you get trouble as in CSS bugs).</p>
<p>IE and hacks</p>
<p>Star html Selector Bug for IE7-</p>
<p>Some examples<br />
<a href="http://www.quirksmode.org/css/csshacks.html" rel="nofollow">css hacks</a></p>
<p>eg * html #container{</p>
<p>}</p>
<p>Other <a href="http://brunildo.org/test/csshacks.html" rel="nofollow">hacks</a> which could be used and are considered save. Though are rarely used.</p>
<p>Advice: avoid hacks at all costs that rely on parser bugs in browsers. </p>
<p>Some advanced CSS3 selectors which are not understood by ALL browsers can be used to target a specific browsers eg IE7 or Opera and filter out others. These hacks do NOT rely on  parser bugs in browsers but are at the same time not really handy (not easy to remember)  and maybe not future proof. Eventually other browsers could catch up and  be able to read them too.</p>
<p>Examples</p>
<p><a href="http://www.brothercake.com/site/resources/reference/xxx/" rel="nofollow">IE7</a><br />
For Opera (CSS queries:<br />
Eg <a href="http://www.fu2k.org/alex/css/hacks/fuzzyspecificity#op8andup" rel="nofollow">@media all and (min-width: 0px)</a></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Fredrik Wärnsberg</title>
		<link>http://fadtastic.net/2006/10/01/one-year-ago-css-hacks/#comment-4850</link>
		<author>Fredrik Wärnsberg</author>
		<pubDate>Sun, 01 Oct 2006 22:58:17 +0000</pubDate>
		<guid>http://fadtastic.net/2006/10/01/one-year-ago-css-hacks/#comment-4850</guid>
					<description>Hacks are sometimes needed. For example the * html hack can fix some slight issues with IE6. As long as you're not importing completely different stylesheets I see no problem at all using smaller hacks to make your site look good across browsers. And really, for 2-3 additional/modified rules, I think that a * html hack (I think you can use +*html for IE7, correct me if I'm wrong though) is a better solution than using conditional comments, at least if you document the hacks you're making with comments in your css-file.</description>
		<content:encoded><![CDATA[<p>Hacks are sometimes needed. For example the * html hack can fix some slight issues with IE6. As long as you&#8217;re not importing completely different stylesheets I see no problem at all using smaller hacks to make your site look good across browsers. And really, for 2-3 additional/modified rules, I think that a * html hack (I think you can use +*html for IE7, correct me if I&#8217;m wrong though) is a better solution than using conditional comments, at least if you document the hacks you&#8217;re making with comments in your css-file.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Kabari</title>
		<link>http://fadtastic.net/2006/10/01/one-year-ago-css-hacks/#comment-4862</link>
		<author>Kabari</author>
		<pubDate>Mon, 02 Oct 2006 06:11:22 +0000</pubDate>
		<guid>http://fadtastic.net/2006/10/01/one-year-ago-css-hacks/#comment-4862</guid>
					<description>For small IE problems I'll use a hack, why not? But generally if there is list of problems, more than 1 or 2, I just work around it. An object of CSS is to add more simplicity and flexibility to our designs anyway, so working around small bugs isn't tough.</description>
		<content:encoded><![CDATA[<p>For small IE problems I&#8217;ll use a hack, why not? But generally if there is list of problems, more than 1 or 2, I just work around it. An object of CSS is to add more simplicity and flexibility to our designs anyway, so working around small bugs isn&#8217;t tough.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
