<?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: CSS Systems: Maintaining your style</title>
	<atom:link href="http://ajaxian.com/archives/css-systems-maintaining-your-style/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/css-systems-maintaining-your-style</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Sat, 20 Mar 2010 13:30:04 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Hans Schmucker</title>
		<link>http://ajaxian.com/archives/css-systems-maintaining-your-style/comment-page-1#comment-267747</link>
		<dc:creator>Hans Schmucker</dc:creator>
		<pubDate>Mon, 29 Sep 2008 12:31:07 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/css-systems-maintaining-your-style#comment-267747</guid>
		<description>I wouldn&#039;t recommend using browser hacks for that... instead just try to limit yourself to the set of instructions that any browser besides IE implement perfectly or almost perfectly... which is a lot. If you&#039;re running into bugs with some complicated behaviour, sit down and try to think of another way to do it... maybe a simpler way. For example, I see people complaining every day that floats don&#039;t work like they expect. They&#039;re right, of course... even non-IE browsers seem to behave differently around floats, but that&#039;s not the point. The point is that 90% of all cases where people are complaining about floats can be solved by using absolute positioning (which is something most people don&#039;t dare to use for some reason, even when it does make sense) or display inline...</description>
		<content:encoded><![CDATA[<p>I wouldn&#8217;t recommend using browser hacks for that&#8230; instead just try to limit yourself to the set of instructions that any browser besides IE implement perfectly or almost perfectly&#8230; which is a lot. If you&#8217;re running into bugs with some complicated behaviour, sit down and try to think of another way to do it&#8230; maybe a simpler way. For example, I see people complaining every day that floats don&#8217;t work like they expect. They&#8217;re right, of course&#8230; even non-IE browsers seem to behave differently around floats, but that&#8217;s not the point. The point is that 90% of all cases where people are complaining about floats can be solved by using absolute positioning (which is something most people don&#8217;t dare to use for some reason, even when it does make sense) or display inline&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TNO</title>
		<link>http://ajaxian.com/archives/css-systems-maintaining-your-style/comment-page-1#comment-267744</link>
		<dc:creator>TNO</dc:creator>
		<pubDate>Mon, 29 Sep 2008 12:08:03 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/css-systems-maintaining-your-style#comment-267744</guid>
		<description>I personally have preferred nesting according to how styles are inherited on a page, since its easier to debug.
.
Never use CSS hacks? Some browsers do need help besides IE you know. Conditional comments are intrusive.
.
Also, if you find yourself drilling down your page often with a lengthy selector, you might want to consider adding another class to the page.</description>
		<content:encoded><![CDATA[<p>I personally have preferred nesting according to how styles are inherited on a page, since its easier to debug.<br />
.<br />
Never use CSS hacks? Some browsers do need help besides IE you know. Conditional comments are intrusive.<br />
.<br />
Also, if you find yourself drilling down your page often with a lengthy selector, you might want to consider adding another class to the page.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
