<?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: The Trouble with CSS Transitions</title>
	<atom:link href="http://www.cuppadev.co.uk/quirks/the-trouble-with-css-transitions/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cuppadev.co.uk/quirks/the-trouble-with-css-transitions/</link>
	<description>Cuppalicious coding!</description>
	<lastBuildDate>Thu, 11 Feb 2010 20:09:59 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: smfr</title>
		<link>http://www.cuppadev.co.uk/quirks/the-trouble-with-css-transitions/comment-page-1/#comment-1182</link>
		<dc:creator>smfr</dc:creator>
		<pubDate>Tue, 24 Nov 2009 05:22:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.cuppadev.co.uk/?p=587#comment-1182</guid>
		<description>We&#039;re happy to get bugs filed on WebKit, with nice little testcases: &lt;a href=&quot;http://bugs.webkit.org&quot; rel=&quot;nofollow&quot;&gt;http://bugs.webkit.org&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>We&#39;re happy to get bugs filed on WebKit, with nice little testcases: <a href="http://bugs.webkit.org" rel="nofollow">http://bugs.webkit.org</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nemesis</title>
		<link>http://www.cuppadev.co.uk/quirks/the-trouble-with-css-transitions/comment-page-1/#comment-1175</link>
		<dc:creator>Nemesis</dc:creator>
		<pubDate>Mon, 26 Oct 2009 09:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.cuppadev.co.uk/?p=587#comment-1175</guid>
		<description>I was having the same problems with webkitTransitionEnd. I was able to work around it by adding a -webkit-transition-delay: 1ms; to my transitions. That makes them fall under the &quot;Transition after a sufficient undefined delay&quot; category. This seems like a bug in webkit.</description>
		<content:encoded><![CDATA[<p>I was having the same problems with webkitTransitionEnd. I was able to work around it by adding a -webkit-transition-delay: 1ms; to my transitions. That makes them fall under the &#8220;Transition after a sufficient undefined delay&#8221; category. This seems like a bug in webkit.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
