<?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>coffeecoders.de &#187; css3</title>
	<atom:link href="http://coffeecoders.de/tag/css3/feed/" rel="self" type="application/rss+xml" />
	<link>http://coffeecoders.de</link>
	<description>professional devs at work</description>
	<lastBuildDate>Tue, 13 Sep 2011 16:34:02 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Web browser capabilities revisited</title>
		<link>http://coffeecoders.de/2009/02/web-browser-capabilities-revisited/</link>
		<comments>http://coffeecoders.de/2009/02/web-browser-capabilities-revisited/#comments</comments>
		<pubDate>Sun, 15 Feb 2009 23:40:04 +0000</pubDate>
		<dc:creator>stevie</dc:creator>
				<category><![CDATA[common]]></category>
		<category><![CDATA[coding]]></category>
		<category><![CDATA[css3]]></category>
		<category><![CDATA[html]]></category>
		<category><![CDATA[link]]></category>
		<category><![CDATA[webdesign]]></category>

		<guid isPermaLink="false">http://coffeecoders.de/?p=178</guid>
		<description><![CDATA[As a web developer you always have to keep in mind that what looks great on your box not always looks that good on your client&#8217;s or on some random visitor&#8217;s screen. This is mostly because of the different browser &#8230; <a href="http://coffeecoders.de/2009/02/web-browser-capabilities-revisited/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>As a web developer you always have to keep in mind that what looks great on your box not always looks that good on your client&#8217;s or on some random visitor&#8217;s screen. This is mostly because of the different browser engines and versions.</p>
<p>With this in mind you might tend to avoid any newer techniques, features or elements just to be on the safe side. But this also keeps you from using shortcuts and often results in worse quality.<br />
<span id="more-178"></span><br />
If you planning to use a newer feature it might help if you knew which users won&#8217;t be able to enjoy your work to the full extend. To help everyone with this problem <em>Alexis Deveria</em> compiled a long list of the features and how are they supported by Internet Explorer, Firefox, Safari, Chrome and Opera. This list is even searchable and customizable to your needs (e.g. exclude browsers).</p>
<p>I can&#8217;t thank him enough for going through all that trouble finding these information and I am certain that this list will have a top spot in my future bookmarks and maybe in your&#8217;s too.</p>
<p>Link: <a href="http://a.deveria.com/caniuse/#agents=All&amp;cats=All&amp;eras=All&amp;statuses=All">When can I use&#8230; &#8211; a huge, searchable list of browser capabilities</a></p>
]]></content:encoded>
			<wfw:commentRss>http://coffeecoders.de/2009/02/web-browser-capabilities-revisited/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Firefox 3.1 &#8211; A Designers&#8217; Release</title>
		<link>http://coffeecoders.de/2009/02/firefox-31-a-designers-release/</link>
		<comments>http://coffeecoders.de/2009/02/firefox-31-a-designers-release/#comments</comments>
		<pubDate>Sat, 14 Feb 2009 01:33:07 +0000</pubDate>
		<dc:creator>Erik</dc:creator>
				<category><![CDATA[common]]></category>
		<category><![CDATA[beta]]></category>
		<category><![CDATA[css3]]></category>
		<category><![CDATA[firefox]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[typography]]></category>

		<guid isPermaLink="false">http://coffeecoders.de/?p=144</guid>
		<description><![CDATA[Many web designers will be pleased to see the list of changes that will be introduced with the upcoming Firefox release 3.1. Many exciting features have been integrated and are awaiting their use in new websites. Some of these are: &#8230; <a href="http://coffeecoders.de/2009/02/firefox-31-a-designers-release/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Many web designers will be pleased to see <a title="Firefox 3.1 complete list of changes">the list of changes</a> that will be introduced with the upcoming Firefox release 3.1. Many exciting features have been integrated and are awaiting their use in new websites. Some of these are: the <code>@font-face</code> rule, which can be used to declare font files (that will be downloaded to the client computer in the background), some new HTML 5 features, an improved color management (allowing for colour correction based on ICC profiles) and JSON-support built directly into the browsers&#8217; <acronym title="Document Object Model">DOM</acronym>.</p>
<p><span id="more-144"></span>There are two changes I consider &#8220;my favorites&#8221;: as Firefox is about to close the gap between itself and the highly innovative Webkit browsers Safari and Chrome, more CSS 3 properties will be supported in Version 3.1. I&#8217;m looking forward to use <code>text-shadow</code> because it simply looks great.<br />
And then there is <code>word-wrap</code>.<br />
Whilst other browsers &#8211; even the worst of them &#8211; have been capable of word splitting for several years, this one has been a major annoyance in Firefox. Now that v3.1 introduces word-wrapping one should be able to use narrow columns more effectively without having to be afraid of (long) words flying outside of their columns. And even for regular dimensioned sidebars, an enhanced typeface is something to look forward to.</p>
]]></content:encoded>
			<wfw:commentRss>http://coffeecoders.de/2009/02/firefox-31-a-designers-release/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

