<?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"
	>
<channel>
	<title>Comments on: Yay for Jacob Seidelin to join me in accessihacking YouTube</title>
	<atom:link href="http://www.wait-till-i.com/2008/06/06/yay-for-jacob-seidelin-to-join-me-in-accessihacking-youtube/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wait-till-i.com/2008/06/06/yay-for-jacob-seidelin-to-join-me-in-accessihacking-youtube/</link>
	<description>Chris Heilmann - Accessibility, Web Development and Pragmatism - can talk, will travel</description>
	<pubDate>Fri, 05 Dec 2008 11:12:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Jacob Seidelin</title>
		<link>http://www.wait-till-i.com/2008/06/06/yay-for-jacob-seidelin-to-join-me-in-accessihacking-youtube/#comment-7820</link>
		<dc:creator>Jacob Seidelin</dc:creator>
		<pubDate>Fri, 06 Jun 2008 16:12:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.wait-till-i.com/2008/06/06/yay-for-jacob-seidelin-to-join-me-in-accessihacking-youtube/#comment-7820</guid>
		<description>Of course, I agree. And I imagine it's just a matter of time before there's a real API available.</description>
		<content:encoded><![CDATA[<p>Of course, I agree. And I imagine it&#8217;s just a matter of time before there&#8217;s a real <span class="caps">API </span>available.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.wait-till-i.com/2008/06/06/yay-for-jacob-seidelin-to-join-me-in-accessihacking-youtube/#comment-7818</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Fri, 06 Jun 2008 14:57:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.wait-till-i.com/2008/06/06/yay-for-jacob-seidelin-to-join-me-in-accessihacking-youtube/#comment-7818</guid>
		<description>Well, as you say it is ugly, and a hack. There is also quite a memory and processing overhead in intercepting the player constantly and calling the getCurrentTime() method. Of course it is a good solution for now, but I'd rather see this in the player API itself, natively than having that extra overhead.</description>
		<content:encoded><![CDATA[<p>Well, as you say it is ugly, and a hack. There is also quite a memory and processing overhead in intercepting the player constantly and calling the getCurrentTime() method. Of course it is a good solution for now, but I&#8217;d rather see this in the player <span class="caps">API </span>itself, natively than having that extra overhead.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob Seidelin</title>
		<link>http://www.wait-till-i.com/2008/06/06/yay-for-jacob-seidelin-to-join-me-in-accessihacking-youtube/#comment-7817</link>
		<dc:creator>Jacob Seidelin</dc:creator>
		<pubDate>Fri, 06 Jun 2008 13:08:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.wait-till-i.com/2008/06/06/yay-for-jacob-seidelin-to-join-me-in-accessihacking-youtube/#comment-7817</guid>
		<description>As long as you get the current time from the ytplayer itself, what's the problem with polling? (other than it being a bit ugly..) If the video pauses for whatever reason, so does the time reported by ytplayer.getCurrentTime(), no?</description>
		<content:encoded><![CDATA[<p>As long as you get the current time from the ytplayer itself, what&#8217;s the problem with polling? (other than it being a bit ugly..) If the video pauses for whatever reason, so does the time reported by ytplayer.getCurrentTime(), no?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
