<?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>thetransient &#187; CSS</title>
	<atom:link href="http://www.thetransient.com/category/web-design/code/css-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thetransient.com</link>
	<description>One designer's web design blog</description>
	<lastBuildDate>Wed, 12 May 2010 17:21:11 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>z-index fixes are sometimes easier than you think</title>
		<link>http://www.thetransient.com/z-index-fixes-are-sometimes-easier-than-you-think/213/</link>
		<comments>http://www.thetransient.com/z-index-fixes-are-sometimes-easier-than-you-think/213/#comments</comments>
		<pubDate>Thu, 05 Feb 2009 05:28:18 +0000</pubDate>
		<dc:creator>Erik Phipps</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[z-index]]></category>

		<guid isPermaLink="false">http://www.thetransient.com/?p=213</guid>
		<description><![CDATA[I ran into the dreaded IE7/IE6 z-index rendering bug today. I knew it was going to show its ugly head once I began troubleshooting the UI component I was working on, but little did I expect it to slide itself behind nearly every element it was supposed to cover! I contemplated a jQuery solution but [...]]]></description>
			<content:encoded><![CDATA[<p>I ran into the dreaded IE7/IE6 z-index rendering bug today. I knew it was going to show its ugly head once I began troubleshooting the UI component I was working on, but little did I expect it to slide itself behind nearly every element it was supposed to cover! I contemplated a jQuery solution but the thought of targeting so many different elements made my head spin.</p>
<p>I started running the causes through my head; position is relative, IE 7, target layer opens below event element&#8230;and then it hit me! Simply position the layer above the event triggering element! It worked because everything above the relative container was rendered before it in the source html. It was like manually reversing the z-index with jQuery except, since it was going in reverse, the browser had stacked the items correctly! Luckily the component I was working on had both the space and design to accomodate such a solution.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.thetransient.com/z-index-fixes-are-sometimes-easier-than-you-think/213/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Build HTML/CSS pages or components from the ground up</title>
		<link>http://www.thetransient.com/build-htmlcss-pages-or-components-from-the-ground-up/221/</link>
		<comments>http://www.thetransient.com/build-htmlcss-pages-or-components-from-the-ground-up/221/#comments</comments>
		<pubDate>Wed, 04 Feb 2009 16:10:44 +0000</pubDate>
		<dc:creator>Erik Phipps</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[Code]]></category>
		<category><![CDATA[HTML]]></category>

		<guid isPermaLink="false">http://www.thetransient.com/?p=221</guid>
		<description><![CDATA[When building HTML/CSS pages or components, I usually follow specific steps in order to keep my code clean and concise. The trick is to start with the base foundation and then slowly drill your way down to the very smallest inline element. These steps aren&#8217;t set in stone of course, and I often mix things [...]]]></description>
			<content:encoded><![CDATA[<p>When building HTML/CSS pages or components, I usually follow specific steps in order to keep my code clean and concise. The trick is to start with the base foundation and then slowly drill your way down to the very smallest inline element. These steps aren&#8217;t set in stone of course, and I often mix things up due to extenuating circumstances.</p>
<ol>
<li>Create raw html code with only the most basic tags and high level block divisions. This step is important to finish first so that anytime after it is done, the markup can be passed on to a developer. Don&#8217;t add ANY CSS until you are done!</li>
<li>Start applying structural styles first to get the basic layout worked out.</li>
<li>Apply any background images on the high level structural elements and/or body.</li>
<li>Apply non-color styles such as padding, margins, font-size, to block level elements, then inline elements if necessary.</li>
<li>Apply final colors and finish any fine-tuning</li>
</ol>
<p>Also, don&#8217;t forget to test in all supported browsers after each step.<br />
]]></content:encoded>
			<wfw:commentRss>http://www.thetransient.com/build-htmlcss-pages-or-components-from-the-ground-up/221/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
