<?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>bitblogr.com &#187; CSS</title>
	<atom:link href="http://www.bitblogr.com/category/css/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bitblogr.com</link>
	<description>design, tutorials, inspiration, creativity</description>
	<lastBuildDate>Sat, 05 Jun 2010 17:20:23 +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: When property/value order matters</title>
		<link>http://www.bitblogr.com/how-to/css-when-propertyvalue-order-matters/</link>
		<comments>http://www.bitblogr.com/how-to/css-when-propertyvalue-order-matters/#comments</comments>
		<pubDate>Thu, 27 Aug 2009 18:08:57 +0000</pubDate>
		<dc:creator>Opeyemi Obembe</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[How-To]]></category>

		<guid isPermaLink="false">http://www.bitblogr.com/?p=67</guid>
		<description><![CDATA[Generally, the believe about CSS is that no matter what order your property or value declaration comes in a selector, it is the same. In other words, thus; *{ margin: 0; padding; 0; } is the same as *{ padding: 0; margin; 0; } But this is not always so. Let’s take a look at [...]]]></description>
			<content:encoded><![CDATA[<div style="float:right;margin:0px 0px 0px 0px;"></div><div class="tweetmeme_button" style="float: right; margin-left: 10px;margin-right:10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.bitblogr.com%2Fhow-to%2Fcss-when-propertyvalue-order-matters%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.bitblogr.com%2Fhow-to%2Fcss-when-propertyvalue-order-matters%2F&amp;source=bitblogr&amp;style=normal&amp;service_api=R_2574ec2cdf93a9dc24a80c02f8d96a25&amp;hashtags=CSS" height="61" width="50" /><br />
			</a>
		</div>
<p>Generally, the believe about CSS is that no matter what order your property or value declaration comes in a selector, it is the same.</p>
<p>In other words, thus;</p>
<pre>*{
margin: 0;

padding; 0;
}<span id="more-67"></span></pre>
<p>is the same as</p>
<pre>*{
padding: 0;

margin; 0;
}</pre>
<p>But this is not always so.</p>
<p><strong>Let’s take a look at borders;</strong></p>
<p>The declarations for borders looks something like this;</p>
<pre>.bordered{
  border: 1px solid #000;
  }</pre>
<p>If you are however interested in just the top and bottom border, you may want to go this way;</p>
<pre>.bordered{
  border-top: 1px solid #000;
  border-bottom: 1px solid #000;
  }</pre>
<p>There is however a short-cut to that. A better way to go should be;</p>
<pre>.bordered{
  border: solid #000;
  border-width: 1px 0;

/* the 1px is for top &amp; bottom, while 0 is for left &amp; right  */
  }</pre>
<p>And that is where the order (which of ‘border’ &amp; ‘border-width’ comes first) matters. If the ordering is reversed (as shown below), it won’t work as expected.</p>
<pre>.bordered{
  border-width: 1px 0;

border: solid #000;

}</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.bitblogr.com/how-to/css-when-propertyvalue-order-matters/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
