<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.7" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Swfobject and lightbox conflict</title>
	<link>http://team.bkwld.com/2008/04/25/swfobject-and-lightbox-conflict/</link>
	<description>Team BKWLD</description>
	<pubDate>Tue, 06 Jan 2009 11:24:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.7</generator>

	<item>
		<title>by: Robert</title>
		<link>http://team.bkwld.com/2008/04/25/swfobject-and-lightbox-conflict/#comment-3097</link>
		<pubDate>Wed, 07 May 2008 20:30:28 +0000</pubDate>
		<guid>http://team.bkwld.com/2008/04/25/swfobject-and-lightbox-conflict/#comment-3097</guid>
					<description>Quick update, the whole defer thing ended up causing some probs in IE 7.  The site ended up not needing lightbox in the end, so I took all of this at.  So it's still sort of a mystery, but something to be solved later.</description>
		<content:encoded><![CDATA[<p>Quick update, the whole defer thing ended up causing some probs in IE 7.  The site ended up not needing lightbox in the end, so I took all of this at.  So it&#8217;s still sort of a mystery, but something to be solved later.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jordan</title>
		<link>http://team.bkwld.com/2008/04/25/swfobject-and-lightbox-conflict/#comment-2804</link>
		<pubDate>Mon, 28 Apr 2008 22:09:11 +0000</pubDate>
		<guid>http://team.bkwld.com/2008/04/25/swfobject-and-lightbox-conflict/#comment-2804</guid>
					<description>Yes Flash Satay is definitely the way to go if you can. With SwfObject though it lends itself to allowing you to detect the player version so you can handle an upgrade if needed. That is something the Satay method doesn't do all that well.

So did do you approach the version detection when you were using the Satay method?</description>
		<content:encoded><![CDATA[<p>Yes Flash Satay is definitely the way to go if you can. With SwfObject though it lends itself to allowing you to detect the player version so you can handle an upgrade if needed. That is something the Satay method doesn&#8217;t do all that well.</p>
<p>So did do you approach the version detection when you were using the Satay method?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mark</title>
		<link>http://team.bkwld.com/2008/04/25/swfobject-and-lightbox-conflict/#comment-2802</link>
		<pubDate>Mon, 28 Apr 2008 17:02:49 +0000</pubDate>
		<guid>http://team.bkwld.com/2008/04/25/swfobject-and-lightbox-conflict/#comment-2802</guid>
					<description>@Aral and @Jordan, the object element is an official W3C recommendation that has progressive enhancement built right in.  &lt;a href="http://www.alistapart.com/articles/flashsatay" rel="nofollow"&gt;Flash Satay&lt;/a&gt; was my method of choice for years, until MS lost their lawsuit with Eolas.  It's perfectly standards compliant, downgrades gracefully when the desired plug-in isn't available, and requires no javascript.  IE is the reason for confusing bits of this implementation, and IE is the reason it is no longer a viable solution (click to activate).</description>
		<content:encoded><![CDATA[<p>@Aral and @Jordan, the object element is an official W3C recommendation that has progressive enhancement built right in.  <a href="http://www.alistapart.com/articles/flashsatay" rel="nofollow">Flash Satay</a> was my method of choice for years, until MS lost their lawsuit with Eolas.  It&#8217;s perfectly standards compliant, downgrades gracefully when the desired plug-in isn&#8217;t available, and requires no javascript.  IE is the reason for confusing bits of this implementation, and IE is the reason it is no longer a viable solution (click to activate).
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jordan</title>
		<link>http://team.bkwld.com/2008/04/25/swfobject-and-lightbox-conflict/#comment-2790</link>
		<pubDate>Sun, 27 Apr 2008 21:57:58 +0000</pubDate>
		<guid>http://team.bkwld.com/2008/04/25/swfobject-and-lightbox-conflict/#comment-2790</guid>
					<description>I would have to agree with Alan. Standards compliant code is good. Are you sure it was a conflict with lightbox. Reading further is seemed it like it was a runtime delay issue.</description>
		<content:encoded><![CDATA[<p>I would have to agree with Alan. Standards compliant code is good. Are you sure it was a conflict with lightbox. Reading further is seemed it like it was a runtime delay issue.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Aral Balkan</title>
		<link>http://team.bkwld.com/2008/04/25/swfobject-and-lightbox-conflict/#comment-2771</link>
		<pubDate>Sun, 27 Apr 2008 11:33:35 +0000</pubDate>
		<guid>http://team.bkwld.com/2008/04/25/swfobject-and-lightbox-conflict/#comment-2771</guid>
					<description>Hey guys, 

Glad to hear that the post helped :) Mark, I'd argue that the main reason for using SWFObject is to embed SWF files in a standards-compliant manner that lends itself to the implementation of progressive enhancement :)</description>
		<content:encoded><![CDATA[<p>Hey guys, </p>
<p>Glad to hear that the post helped :) Mark, I&#8217;d argue that the main reason for using SWFObject is to embed SWF files in a standards-compliant manner that lends itself to the implementation of progressive enhancement :)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mark</title>
		<link>http://team.bkwld.com/2008/04/25/swfobject-and-lightbox-conflict/#comment-2770</link>
		<pubDate>Sat, 26 Apr 2008 22:07:00 +0000</pubDate>
		<guid>http://team.bkwld.com/2008/04/25/swfobject-and-lightbox-conflict/#comment-2770</guid>
					<description>I never would have guessed that would be the problem. The primary reason for using swf object is for IE compatibility. If they have such a hard time keeping up with the Internet, why don't they just license webkit?</description>
		<content:encoded><![CDATA[<p>I never would have guessed that would be the problem. The primary reason for using swf object is for IE compatibility. If they have such a hard time keeping up with the Internet, why don&#8217;t they just license webkit?
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
