<?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>Jon Raasch&#039;s Blog &#187; CSS</title>
	<atom:link href="http://jonraasch.com/blog/category/css/feed" rel="self" type="application/rss+xml" />
	<link>http://jonraasch.com/blog</link>
	<description>Web development and design blog from Portland based developer Jon Raasch</description>
	<lastBuildDate>Thu, 13 Oct 2011 15:27:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<atom:link rel="next" href="http://jonraasch.com/blog/category/css/feed?page=2" />

		<item>
		<title>CSS Data URIs &#8211; Use Them In All Browsers Now!</title>
		<link>http://jonraasch.com/blog/css-data-uris-in-all-browsers</link>
		<comments>http://jonraasch.com/blog/css-data-uris-in-all-browsers#comments</comments>
		<pubDate>Wed, 10 Nov 2010 18:30:23 +0000</pubDate>
		<dc:creator>Jon Raasch</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[cross-browser]]></category>
		<category><![CDATA[data URIs]]></category>
		<category><![CDATA[front-end]]></category>
		<category><![CDATA[HTTP requests]]></category>
		<category><![CDATA[performance]]></category>

		<guid isPermaLink="false">http://jonraasch.com/blog/?p=1233</guid>
		<description><![CDATA[<a href="http://www.nczonline.net/blog/2009/10/27/data-uris-explained/">Data URIs</a> are one of the best techniques in CSS, allowing developers to avoid referencing external images and instead embed them directly into a stylesheet.  The main advantage of this approach is to save <a href="http://djce.org.uk/dumprequest">HTTP requests</a>.

HTTP requests are a huge <strong>performance bottleneck</strong>, and the reason techniques such as <a href="http://www.alistapart.com/articles/sprites">CSS image sprites</a> have been popular for some time.  Basically, if you can avoid requesting an extra file, not only does it save your server the work of looking up the file, but it also saves your user the download time.  In fact, HTTP request management is so important, that it is the top issue in the <a href="http://developer.yahoo.com/performance/rules.html">Yahoo Performance Rules</a>.

Data URIs are an excellent way to reduce HTTP requests and <strong>speed up your pages</strong>, so let's walk through how to use them in <strong>all major browsers</strong>.]]></description>
		<wfw:commentRss>http://jonraasch.com/blog/css-data-uris-in-all-browsers/feed</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
		<item>
		<title>Graceful Degradation With CSS3</title>
		<link>http://jonraasch.com/blog/graceful-degradation-with-css3</link>
		<comments>http://jonraasch.com/blog/graceful-degradation-with-css3#comments</comments>
		<pubDate>Tue, 17 Aug 2010 16:57:51 +0000</pubDate>
		<dc:creator>Jon Raasch</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[browser hacks]]></category>
		<category><![CDATA[cross-browser]]></category>
		<category><![CDATA[css3]]></category>
		<category><![CDATA[front-end]]></category>
		<category><![CDATA[graceful degradation]]></category>
		<category><![CDATA[IE]]></category>
		<category><![CDATA[jQuery]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[webdev]]></category>

		<guid isPermaLink="false">http://jonraasch.com/blog/?p=1192</guid>
		<description><![CDATA[With IE9 in development and Opera 10.5 released, CSS3 is a few steps away from being supported by all modern browsers. But users may take a while to upgrade, and responsible developers will support legacy browsers for years to come.

For some, <strong>cross-browser development</strong> means making websites that look exactly the same in all browsers. But if developers continue to cater websites to inadequate browsers such as IE6, then they're just holding back modern browsers from performing to their potential.

<strong>Graceful degradation</strong> is not about allowing websites to look bad in older browsers, but about making them look great in modern ones.  It means taking advantage of CSS3's useful features to progressively enhance web pages for the vast majority of users.]]></description>
		<wfw:commentRss>http://jonraasch.com/blog/graceful-degradation-with-css3/feed</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>CSS Summit: The Good Parts</title>
		<link>http://jonraasch.com/blog/css-summit</link>
		<comments>http://jonraasch.com/blog/css-summit#comments</comments>
		<pubDate>Thu, 29 Jul 2010 16:33:06 +0000</pubDate>
		<dc:creator>Jon Raasch</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[best practices]]></category>
		<category><![CDATA[conferences]]></category>
		<category><![CDATA[cross-browser]]></category>
		<category><![CDATA[css3]]></category>
		<category><![CDATA[front-end]]></category>
		<category><![CDATA[html5]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[webdev]]></category>

		<guid isPermaLink="false">http://jonraasch.com/blog/?p=1124</guid>
		<description><![CDATA[Yesterday's <a href="http://environmentsforhumans.com/2010/css-summit/">CSS Summit</a> featured some the best CSS minds presenting on cutting edge CSS issues.  There was a ton of great information presented across the 8 sessions, but here's a wrap up of the single best piece of information from each presenter:

<h2>Denise Jacobs &#8211; Advanced CSS Troubleshooting</h2>

The highlight of Denise's talk was some specific coding tips about <a href="http://www.quirksmode.org/css/clearing.html">clearing floated content</a>.  

She started with the standard <code>overflow: hidden</code> method, which falls short with support for borders &#38; margins and also doesn't allow scrollbars if they're needed.  Denise suggested instead using <code>overflow: auto; width: 100%;</code> which avoids these issues.  You don't have to use the exact values above, you just have to set some type of <code>overflow</code> and <code>width</code> / <code>height</code> value.

Denise went on to discuss a <code>.clearfix:after</code> method, <a href="http://gist.github.com/498554">see the gist</a>.

Denise likes this clearing method since it doesn't include any extra, non-semantic markup (as opposed to <code>&#60;br class="clearfix" /&#62;</code>).  However the fact that the <code>:after</code> selector doesn't work in IE6/7 makes this method unusable in my opinion.  Ultimately I'm going to stick to the <code>overflow: auto;</code> method described above.]]></description>
		<wfw:commentRss>http://jonraasch.com/blog/css-summit/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Great Examples of Drawing With CSS</title>
		<link>http://jonraasch.com/blog/drawing-with-css</link>
		<comments>http://jonraasch.com/blog/drawing-with-css#comments</comments>
		<pubDate>Tue, 30 Mar 2010 17:34:15 +0000</pubDate>
		<dc:creator>Jon Raasch</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[best practices]]></category>
		<category><![CDATA[cross-browser]]></category>
		<category><![CDATA[css3]]></category>
		<category><![CDATA[rendering]]></category>
		<category><![CDATA[UI]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[webdev]]></category>

		<guid isPermaLink="false">http://jonraasch.com/blog/?p=964</guid>
		<description><![CDATA[<a href="http://jonraasch.com/blog/drawing-with-css" title="Great Examples of Drawing With CSS"><div class="rightImg"><img src="http://jonraasch.com/blog/wp-content/uploads/2010/03/css-raindrop1.jpg" width="249" height="232" alt="Great Examples of Drawing With CSS" /></div></a>I&#8217;ve always been a fan of drawing page components with pure CSS rather than using image support. Although rendering the page with CSS can sometimes be a pain, the rewards of fewer HTTP requests &#38; less download time make it well worthwhile. Until recently, most web designers and developers couldn&#8217;t design using CSS alone, because [...]]]></description>
		<wfw:commentRss>http://jonraasch.com/blog/drawing-with-css/feed</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>CSS Rounded Corners In All Browsers (With No Images)</title>
		<link>http://jonraasch.com/blog/css-rounded-corners-in-all-browsers</link>
		<comments>http://jonraasch.com/blog/css-rounded-corners-in-all-browsers#comments</comments>
		<pubDate>Thu, 04 Feb 2010 18:00:19 +0000</pubDate>
		<dc:creator>Jon Raasch</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[cross-browser]]></category>
		<category><![CDATA[CSS hacks]]></category>
		<category><![CDATA[css3]]></category>
		<category><![CDATA[IE]]></category>
		<category><![CDATA[Opera]]></category>
		<category><![CDATA[rounded corners]]></category>
		<category><![CDATA[SVG]]></category>
		<category><![CDATA[vector]]></category>

		<guid isPermaLink="false">http://jonraasch.com/blog/?p=628</guid>
		<description><![CDATA[<a href="http://jonraasch.com/blog/css-rounded-corners-in-all-browsers" title="CSS Rounded Corners In All Browsers (With No Images)"><div class="rightImg"><img src="http://jonraasch.com/blog/wp-content/uploads/2010/02/cross-browser.png" width="300" height="267" alt="CSS Rounded Corners In All Browsers (With No Images)" /></div></a>In the past two years, increased browser support has transformed CSS3 from a fringe activity for Safari geeks to a viable option for enterprise level websites. While cross-browser support is often too weak for CSS3 to hold up a site&#8217;s main design, front-end developers commonly look to CSS3 solutions for progressive enhancement in their sites. [...]]]></description>
		<wfw:commentRss>http://jonraasch.com/blog/css-rounded-corners-in-all-browsers/feed</wfw:commentRss>
		<slash:comments>159</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
