<?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: Small bits</title>
	<atom:link href="http://kilianvalkhof.com/2008/web/small-bits/feed/" rel="self" type="application/rss+xml" />
	<link>http://kilianvalkhof.com/2008/web/small-bits/</link>
	<description></description>
	<lastBuildDate>Sun, 13 May 2012 19:51:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: NatalieMac</title>
		<link>http://kilianvalkhof.com/2008/web/small-bits/comment-page-1/#comment-6851</link>
		<dc:creator>NatalieMac</dc:creator>
		<pubDate>Wed, 02 Jul 2008 04:53:00 +0000</pubDate>
		<guid isPermaLink="false">http://kilianvalkhof.com/?p=73#comment-6851</guid>
		<description>You&#039;re right - body{cursor:none;} is probably not such a good idea. But it&#039;s pretty handy to be able to hide cursors over video (just not the video controls!)</description>
		<content:encoded><![CDATA[<p>You&#8217;re right &#8211; body{cursor:none;} is probably not such a good idea. But it&#8217;s pretty handy to be able to hide cursors over video (just not the video controls!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Moving forward with CSS &#124; Wisdump</title>
		<link>http://kilianvalkhof.com/2008/web/small-bits/comment-page-1/#comment-6796</link>
		<dc:creator>Moving forward with CSS &#124; Wisdump</dc:creator>
		<pubDate>Mon, 30 Jun 2008 06:35:14 +0000</pubDate>
		<guid isPermaLink="false">http://kilianvalkhof.com/?p=73#comment-6796</guid>
		<description>[...] 3: Killian Valkhof and David Baron write about support for several CSS3 features in the latest version of Mozilla [...]</description>
		<content:encoded><![CDATA[<p>[...] 3: Killian Valkhof and David Baron write about support for several CSS3 features in the latest version of Mozilla [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kilian Valkhof</title>
		<link>http://kilianvalkhof.com/2008/web/small-bits/comment-page-1/#comment-6665</link>
		<dc:creator>Kilian Valkhof</dc:creator>
		<pubDate>Mon, 23 Jun 2008 20:19:56 +0000</pubDate>
		<guid isPermaLink="false">http://kilianvalkhof.com/?p=73#comment-6665</guid>
		<description>You bring up an interesting point. There is indeed a growing disparity between pretty much every &quot;current generation&quot; browsers in terms of CSS support. 

However, I believe this happened back in the netscape/IE days as well. ACID tests somehow rectified that, but it&#039;s making our lived unnecessarily harder.

I think Firefox and Opera take a good stand here, actually implementing written specifications. Safari (with animations, masks and whatnot) and IE (with, well, uhm...) are adding the garnish that&#039;s not even spec&#039;d yet.

I think this idea is worth exploring some more :)</description>
		<content:encoded><![CDATA[<p>You bring up an interesting point. There is indeed a growing disparity between pretty much every &#8220;current generation&#8221; browsers in terms of CSS support. </p>
<p>However, I believe this happened back in the netscape/IE days as well. ACID tests somehow rectified that, but it&#8217;s making our lived unnecessarily harder.</p>
<p>I think Firefox and Opera take a good stand here, actually implementing written specifications. Safari (with animations, masks and whatnot) and IE (with, well, uhm&#8230;) are adding the garnish that&#8217;s not even spec&#8217;d yet.</p>
<p>I think this idea is worth exploring some more :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jono Alderson</title>
		<link>http://kilianvalkhof.com/2008/web/small-bits/comment-page-1/#comment-6664</link>
		<dc:creator>Jono Alderson</dc:creator>
		<pubDate>Mon, 23 Jun 2008 20:10:13 +0000</pubDate>
		<guid isPermaLink="false">http://kilianvalkhof.com/?p=73#comment-6664</guid>
		<description>As ever, lots of very exciting new features!
 
However, with the standard practice being to generally provide full support for at the very least the two previous significant generations of browsers, and partial-to-complete support for anything older / with less capable rendering engines whenever possible, all we&#039;re really looking at is garnish that&#039;ll increasingly add to browser disparity and fragmentation. 

Having said that, I&#039;m all for making use of these new features and the rest of CSS 3 as it becomes available - it just seems a shame that it&#039;s shadowed by the fact that it&#039;s yet another contribution to cross-browser compatibility issues.</description>
		<content:encoded><![CDATA[<p>As ever, lots of very exciting new features!</p>
<p>However, with the standard practice being to generally provide full support for at the very least the two previous significant generations of browsers, and partial-to-complete support for anything older / with less capable rendering engines whenever possible, all we&#8217;re really looking at is garnish that&#8217;ll increasingly add to browser disparity and fragmentation. </p>
<p>Having said that, I&#8217;m all for making use of these new features and the rest of CSS 3 as it becomes available &#8211; it just seems a shame that it&#8217;s shadowed by the fact that it&#8217;s yet another contribution to cross-browser compatibility issues.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

