<?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: Why it&#8217;s a Good Time to Play with Webkit CSS Properties</title>
	<atom:link href="http://www.chrispalle.com/2008/04/26/why-its-a-good-time-to-play-with-css-webkit-properties/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.chrispalle.com/2008/04/26/why-its-a-good-time-to-play-with-css-webkit-properties/</link>
	<description></description>
	<lastBuildDate>Sun, 21 Feb 2010 15:23:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: puppies for sale</title>
		<link>http://www.chrispalle.com/2008/04/26/why-its-a-good-time-to-play-with-css-webkit-properties/comment-page-1/#comment-1878</link>
		<dc:creator>puppies for sale</dc:creator>
		<pubDate>Mon, 14 Sep 2009 09:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrispalle.com/?p=120#comment-1878</guid>
		<description>I don’t see any valid reason for that? Exactly why are you suggesting that? Why will I be ready to change the practice of having the one I use and use this one instead? </description>
		<content:encoded><![CDATA[<p>I don’t see any valid reason for that? Exactly why are you suggesting that? Why will I be ready to change the practice of having the one I use and use this one instead?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Google Chrome Announced &#124; Refined by Fire</title>
		<link>http://www.chrispalle.com/2008/04/26/why-its-a-good-time-to-play-with-css-webkit-properties/comment-page-1/#comment-1528</link>
		<dc:creator>Google Chrome Announced &#124; Refined by Fire</dc:creator>
		<pubDate>Tue, 02 Sep 2008 16:04:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrispalle.com/?p=120#comment-1528</guid>
		<description>[...] and Adobe took Webkit to mainstream adoption, but Google has also announced their use of it. I called it months ago. Now is great time to start using Webkit as a primary starting point for Web design and [...]</description>
		<content:encoded><![CDATA[<p>[...] and Adobe took Webkit to mainstream adoption, but Google has also announced their use of it. I called it months ago. Now is great time to start using Webkit as a primary starting point for Web design and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chrispy</title>
		<link>http://www.chrispalle.com/2008/04/26/why-its-a-good-time-to-play-with-css-webkit-properties/comment-page-1/#comment-1221</link>
		<dc:creator>chrispy</dc:creator>
		<pubDate>Sun, 27 Apr 2008 11:23:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrispalle.com/?p=120#comment-1221</guid>
		<description>Lars, thanks for your input. Opera is a great browser, no doubt. To be honest, I made the mistake and did not consider it when I wrote this. I don&#039;t think Opera is gaining the same traction in adoption as Webkit. And I think the support for innerHTML has been largely worked out and if not, it is on its way. FF is certainly a stronger browser in this regard and leading in usage, but it&#039;s so darn pokey. I think for general browsing, we&#039;re going to see a leap in Webkit usage because of Safari, AIR, and Nokia.

The point I&#039;m making is not to get hung up on the introduction of non-standard techniques and avoid them in this case. Some think that the addition of these properties is going to debilitate their code. If you practice sound coding tactics like progressive enhancement, you&#039;ll avoid much of the troubles of future (non)compliance.

And I totally agree with you that the potential for abuse is high, but as with any technology, those who improperly use it will be sifted out and *hopefully* learn from the mistakes.</description>
		<content:encoded><![CDATA[<p>Lars, thanks for your input. Opera is a great browser, no doubt. To be honest, I made the mistake and did not consider it when I wrote this. I don&#8217;t think Opera is gaining the same traction in adoption as Webkit. And I think the support for innerHTML has been largely worked out and if not, it is on its way. FF is certainly a stronger browser in this regard and leading in usage, but it&#8217;s so darn pokey. I think for general browsing, we&#8217;re going to see a leap in Webkit usage because of Safari, AIR, and Nokia.</p>
<p>The point I&#8217;m making is not to get hung up on the introduction of non-standard techniques and avoid them in this case. Some think that the addition of these properties is going to debilitate their code. If you practice sound coding tactics like progressive enhancement, you&#8217;ll avoid much of the troubles of future (non)compliance.</p>
<p>And I totally agree with you that the potential for abuse is high, but as with any technology, those who improperly use it will be sifted out and *hopefully* learn from the mistakes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lars Gunther</title>
		<link>http://www.chrispalle.com/2008/04/26/why-its-a-good-time-to-play-with-css-webkit-properties/comment-page-1/#comment-1220</link>
		<dc:creator>Lars Gunther</dc:creator>
		<pubDate>Sun, 27 Apr 2008 09:42:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrispalle.com/?p=120#comment-1220</guid>
		<description>To say that Webkit is &quot;above the rest&quot; is really not true. Acid3 is not the end of standards compliance. Opera support 90 % of all SVG tests. Webkit only half of them. Webkit mistreats the (being standardized) innerHTML method. Firefox support is rock solid - and innerHTML is way more important than many of the obscure parts of Acid3. Opera is way ahead on Web Forms 2.0. Firefox is way ahead on JavaScript. And, oh, yeah, Opera actually beat Webkit to the 100 score by 40 minutes...

I am not saying Webkit is bad. It gets some things right that no one else does. It is a bit behind on other features. As for this new stuff: Transitions may one day become a usable standard. Today the potential for abuse is way too high. Gradients is a much better proposal.</description>
		<content:encoded><![CDATA[<p>To say that Webkit is &#8220;above the rest&#8221; is really not true. Acid3 is not the end of standards compliance. Opera support 90 % of all SVG tests. Webkit only half of them. Webkit mistreats the (being standardized) innerHTML method. Firefox support is rock solid &#8211; and innerHTML is way more important than many of the obscure parts of Acid3. Opera is way ahead on Web Forms 2.0. Firefox is way ahead on JavaScript. And, oh, yeah, Opera actually beat Webkit to the 100 score by 40 minutes&#8230;</p>
<p>I am not saying Webkit is bad. It gets some things right that no one else does. It is a bit behind on other features. As for this new stuff: Transitions may one day become a usable standard. Today the potential for abuse is way too high. Gradients is a much better proposal.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
