<?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: 15 CSS Habits to Develop for Frustration-Free Coding</title>
	<atom:link href="http://www.noupe.com/css/15-css-habits-to-develop-for-frustration-free-coding.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.noupe.com/css/15-css-habits-to-develop-for-frustration-free-coding.html</link>
	<description>The Curious Side of Smashing Magazine</description>
	<lastBuildDate>Sat, 11 Feb 2012 18:35:31 +0100</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Hannes</title>
		<link>http://www.noupe.com/css/15-css-habits-to-develop-for-frustration-free-coding.html/comment-page-1#comment-1082901</link>
		<dc:creator>Hannes</dc:creator>
		<pubDate>Tue, 30 Aug 2011 10:21:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.noupe.com/?p=41094#comment-1082901</guid>
		<description>One could use * { position: relative } which is quite intuitive. And it fixes some hasLayout problems in ie6 and 7.

When styling buttons, I go with button tag. It works cross browser if done right. One of the most important things I figured out with buttons is that never use line-height on button tag because it&#039;s overwritten by Firefoxes own css. So add line-height to span inside button tag.

Made an example here: http://jsfiddle.net/hkirsman/fmpg2/</description>
		<content:encoded><![CDATA[<p>One could use * { position: relative } which is quite intuitive. And it fixes some hasLayout problems in ie6 and 7.</p>
<p>When styling buttons, I go with button tag. It works cross browser if done right. One of the most important things I figured out with buttons is that never use line-height on button tag because it&#8217;s overwritten by Firefoxes own css. So add line-height to span inside button tag.</p>
<p>Made an example here: <a href="http://jsfiddle.net/hkirsman/fmpg2/" rel="nofollow">http://jsfiddle.net/hkirsman/fmpg2/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Sammut</title>
		<link>http://www.noupe.com/css/15-css-habits-to-develop-for-frustration-free-coding.html/comment-page-1#comment-1023632</link>
		<dc:creator>Ryan Sammut</dc:creator>
		<pubDate>Fri, 19 Aug 2011 13:01:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.noupe.com/?p=41094#comment-1023632</guid>
		<description>The most important one here is rule number 1, just don&#039;t forget to do it. I used to code for about 3 - 6 months without knowing about this, and used to encounter lots of problems. With a reset stylesheet, you would solve 90% of the problems.</description>
		<content:encoded><![CDATA[<p>The most important one here is rule number 1, just don&#8217;t forget to do it. I used to code for about 3 &#8211; 6 months without knowing about this, and used to encounter lots of problems. With a reset stylesheet, you would solve 90% of the problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glow74ind</title>
		<link>http://www.noupe.com/css/15-css-habits-to-develop-for-frustration-free-coding.html/comment-page-1#comment-923521</link>
		<dc:creator>Glow74ind</dc:creator>
		<pubDate>Wed, 13 Jul 2011 14:04:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.noupe.com/?p=41094#comment-923521</guid>
		<description>#15, its not true. I have tried it and I am using it.
It does not create addition line-height for the  tag content.</description>
		<content:encoded><![CDATA[<p>#15, its not true. I have tried it and I am using it.<br />
It does not create addition line-height for the  tag content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig McPheat</title>
		<link>http://www.noupe.com/css/15-css-habits-to-develop-for-frustration-free-coding.html/comment-page-1#comment-847107</link>
		<dc:creator>Craig McPheat</dc:creator>
		<pubDate>Mon, 13 Jun 2011 11:15:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.noupe.com/?p=41094#comment-847107</guid>
		<description>Great article; I&#039;m going to hold onto ems over px until my stats get rid of the older browsers :)</description>
		<content:encoded><![CDATA[<p>Great article; I&#8217;m going to hold onto ems over px until my stats get rid of the older browsers :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Templates Perfect</title>
		<link>http://www.noupe.com/css/15-css-habits-to-develop-for-frustration-free-coding.html/comment-page-1#comment-606798</link>
		<dc:creator>Templates Perfect</dc:creator>
		<pubDate>Sun, 20 Mar 2011 06:29:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.noupe.com/?p=41094#comment-606798</guid>
		<description>There are some simple and good CSS techniques worth reading.</description>
		<content:encoded><![CDATA[<p>There are some simple and good CSS techniques worth reading.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will</title>
		<link>http://www.noupe.com/css/15-css-habits-to-develop-for-frustration-free-coding.html/comment-page-1#comment-585181</link>
		<dc:creator>Will</dc:creator>
		<pubDate>Tue, 08 Mar 2011 16:48:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.noupe.com/?p=41094#comment-585181</guid>
		<description>I&#039;m terrible at not documenting my CSS and breaking it up into sections. 

I know some people will go as far as creating a kind of &#039;contents&#039; at the start of the CSS file that lets you know how everything is broken down in the file. I know that it&#039;s good practice, but I just never seem to have the time to do that on a client project! 

Something I need to work on I&#039;m sure!</description>
		<content:encoded><![CDATA[<p>I&#8217;m terrible at not documenting my CSS and breaking it up into sections. </p>
<p>I know some people will go as far as creating a kind of &#8216;contents&#8217; at the start of the CSS file that lets you know how everything is broken down in the file. I know that it&#8217;s good practice, but I just never seem to have the time to do that on a client project! </p>
<p>Something I need to work on I&#8217;m sure!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

