<?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: The Fix for the Patch.. I say NO!</title>
	<atom:link href="http://www.neurofuzzy.net/2006/03/09/the-fix-for-the-patch-i-say-no/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.neurofuzzy.net/2006/03/09/the-fix-for-the-patch-i-say-no/</link>
	<description>Geoff Gaudreault's Flash weblog and source files archive.</description>
	<pubDate>Wed, 19 Nov 2008 04:11:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Matt</title>
		<link>http://www.neurofuzzy.net/2006/03/09/the-fix-for-the-patch-i-say-no/#comment-771</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Tue, 25 Apr 2006 12:43:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.neurofuzzy.net/2006/03/09/the-fix-for-the-patch-i-say-no/#comment-771</guid>
		<description>I agree that this javascript fix is backwards thinking.
However, there are already people who are capitalizing 
on this stupid fix, making software to create the code.

Do you have an alternative/better way to apply a fix 
that will still work in IE?

Thanks.</description>
		<content:encoded><![CDATA[<p>I agree that this javascript fix is backwards thinking.<br />
However, there are already people who are capitalizing<br />
on this stupid fix, making software to create the code.</p>
<p>Do you have an alternative/better way to apply a fix<br />
that will still work in IE?</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Internet</title>
		<link>http://www.neurofuzzy.net/2006/03/09/the-fix-for-the-patch-i-say-no/#comment-596</link>
		<dc:creator>Internet</dc:creator>
		<pubDate>Sun, 16 Apr 2006 04:10:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.neurofuzzy.net/2006/03/09/the-fix-for-the-patch-i-say-no/#comment-596</guid>
		<description>Thanks for the information!  I've been looking all over for an answer to this problem.</description>
		<content:encoded><![CDATA[<p>Thanks for the information!  I&#8217;ve been looking all over for an answer to this problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MOLOKO</title>
		<link>http://www.neurofuzzy.net/2006/03/09/the-fix-for-the-patch-i-say-no/#comment-579</link>
		<dc:creator>MOLOKO</dc:creator>
		<pubDate>Wed, 12 Apr 2006 14:07:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.neurofuzzy.net/2006/03/09/the-fix-for-the-patch-i-say-no/#comment-579</guid>
		<description>I don't think it's a 'hack' at all. Personally I've always used JavaScript to write out the flash object because it lets me do it in two lines of JavaScript instead of many lines of HTML - and also helps to eliminate possible bugs that can creep in due to updating a value in the OBJECT tag then forgetting to do it in the EMBED tag.

I also don't think that 'it relies on having JavaScript turned on' is a convincing argument - it's easy enough to set up your code in such a way that it warns the user if they're got JavaScript switched off and tells them they need it switched.

Your comment about search engines is very valid though, although I'm sure there must be other ways of ensuring a search engine can index your content.

What winds me up about all this is that the EOLAS patent only applies in the USA - yet Microsoft's response to it affects users and developers all over the world. Only users in the States should be obliged to apply the patch - maybe then americans will realise how stupid software patents are and stop using them!</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think it&#8217;s a &#8216;hack&#8217; at all. Personally I&#8217;ve always used JavaScript to write out the flash object because it lets me do it in two lines of JavaScript instead of many lines of HTML - and also helps to eliminate possible bugs that can creep in due to updating a value in the OBJECT tag then forgetting to do it in the EMBED tag.</p>
<p>I also don&#8217;t think that &#8216;it relies on having JavaScript turned on&#8217; is a convincing argument - it&#8217;s easy enough to set up your code in such a way that it warns the user if they&#8217;re got JavaScript switched off and tells them they need it switched.</p>
<p>Your comment about search engines is very valid though, although I&#8217;m sure there must be other ways of ensuring a search engine can index your content.</p>
<p>What winds me up about all this is that the EOLAS patent only applies in the USA - yet Microsoft&#8217;s response to it affects users and developers all over the world. Only users in the States should be obliged to apply the patch - maybe then americans will realise how stupid software patents are and stop using them!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bunnyhero</title>
		<link>http://www.neurofuzzy.net/2006/03/09/the-fix-for-the-patch-i-say-no/#comment-380</link>
		<dc:creator>bunnyhero</dc:creator>
		<pubDate>Sun, 12 Mar 2006 18:12:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.neurofuzzy.net/2006/03/09/the-fix-for-the-patch-i-say-no/#comment-380</guid>
		<description>another positive vote for flashobject from me!

it's too bad embed got deprecated, because it's still the tag that is most reliably and consistently rendered across browsers and platforms.</description>
		<content:encoded><![CDATA[<p>another positive vote for flashobject from me!</p>
<p>it&#8217;s too bad embed got deprecated, because it&#8217;s still the tag that is most reliably and consistently rendered across browsers and platforms.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Giotta</title>
		<link>http://www.neurofuzzy.net/2006/03/09/the-fix-for-the-patch-i-say-no/#comment-366</link>
		<dc:creator>John Giotta</dc:creator>
		<pubDate>Fri, 10 Mar 2006 03:48:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.neurofuzzy.net/2006/03/09/the-fix-for-the-patch-i-say-no/#comment-366</guid>
		<description>I'm sorry, but I absolutely love FlashObject and since I started using it last year all my applications are now completely unaffected by this patch. http://osflash.org/flashobject</description>
		<content:encoded><![CDATA[<p>I&#8217;m sorry, but I absolutely love FlashObject and since I started using it last year all my applications are now completely unaffected by this patch. <a href="http://osflash.org/flashobject" rel="nofollow">http://osflash.org/flashobject</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://www.neurofuzzy.net/2006/03/09/the-fix-for-the-patch-i-say-no/#comment-365</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Fri, 10 Mar 2006 02:29:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.neurofuzzy.net/2006/03/09/the-fix-for-the-patch-i-say-no/#comment-365</guid>
		<description>I'm with you on this one.. I don't like the hack at all..  but..  I'll probably cave in and use it on my pages rather than punish the users for a problem that Microsoft created.  hmm..  maybe I should add something in the doc.write so a message is displayed for IE users.  Or better yet, send them to a random page on Microsoft.com.  Let's see them find something useful on that site.</description>
		<content:encoded><![CDATA[<p>I&#8217;m with you on this one.. I don&#8217;t like the hack at all..  but..  I&#8217;ll probably cave in and use it on my pages rather than punish the users for a problem that Microsoft created.  hmm..  maybe I should add something in the doc.write so a message is displayed for IE users.  Or better yet, send them to a random page on Microsoft.com.  Let&#8217;s see them find something useful on that site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Dowdell</title>
		<link>http://www.neurofuzzy.net/2006/03/09/the-fix-for-the-patch-i-say-no/#comment-364</link>
		<dc:creator>John Dowdell</dc:creator>
		<pubDate>Fri, 10 Mar 2006 02:04:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.neurofuzzy.net/2006/03/09/the-fix-for-the-patch-i-say-no/#comment-364</guid>
		<description>&lt;em&gt;"We are going back to W3C standards as Object and Embed were never part of HTML to begin with."&lt;/em&gt;

They actually were. The spec was, in my opinion at the time and now, in error in not advising how the world could migrate to their new platonic ideal. (The spec outlawed EMBED many years after it was in realworld use, and when I asked on web-standards lists in the late 90s "how will we migrate?" I could never pull a reply.)

That's an interesting point, about "How will search engines react to the JavaScript document.write which the patent requires?" My first take is that bodytext is overrated as a search qualifier anyway... usually it's the inbound links which determine things (cf "Googlebombing"), and after that the TITLE, metadata and other standard qualifiers which play more of a role than bodytext. But it's an interesting question you raise here, one I hadn't heard before, and I'd like to think on it some more....

(Yes, JAWS and WindowEyez do understand dynamically-added content... Andrew Kirkpatrick tested results &lt;a href="http://weblogs.macromedia.com/accessibility/archives/2005/08/in_search_of_a.cfm" rel="nofollow"&gt;here&lt;/a&gt;.)</description>
		<content:encoded><![CDATA[<p><em>&#8220;We are going back to W3C standards as Object and Embed were never part of HTML to begin with.&#8221;</em></p>
<p>They actually were. The spec was, in my opinion at the time and now, in error in not advising how the world could migrate to their new platonic ideal. (The spec outlawed EMBED many years after it was in realworld use, and when I asked on web-standards lists in the late 90s &#8220;how will we migrate?&#8221; I could never pull a reply.)</p>
<p>That&#8217;s an interesting point, about &#8220;How will search engines react to the JavaScript document.write which the patent requires?&#8221; My first take is that bodytext is overrated as a search qualifier anyway&#8230; usually it&#8217;s the inbound links which determine things (cf &#8220;Googlebombing&#8221;), and after that the TITLE, metadata and other standard qualifiers which play more of a role than bodytext. But it&#8217;s an interesting question you raise here, one I hadn&#8217;t heard before, and I&#8217;d like to think on it some more&#8230;.</p>
<p>(Yes, JAWS and WindowEyez do understand dynamically-added content&#8230; Andrew Kirkpatrick tested results <a href="http://weblogs.macromedia.com/accessibility/archives/2005/08/in_search_of_a.cfm" rel="nofollow">here</a>.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://www.neurofuzzy.net/2006/03/09/the-fix-for-the-patch-i-say-no/#comment-363</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Fri, 10 Mar 2006 01:07:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.neurofuzzy.net/2006/03/09/the-fix-for-the-patch-i-say-no/#comment-363</guid>
		<description>HERE HERE!!!   Couldn't have said it better myself.</description>
		<content:encoded><![CDATA[<p>HERE HERE!!!   Couldn&#8217;t have said it better myself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MK</title>
		<link>http://www.neurofuzzy.net/2006/03/09/the-fix-for-the-patch-i-say-no/#comment-362</link>
		<dc:creator>MK</dc:creator>
		<pubDate>Fri, 10 Mar 2006 00:45:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.neurofuzzy.net/2006/03/09/the-fix-for-the-patch-i-say-no/#comment-362</guid>
		<description>We are going back to W3C standards as Object and Embed were never part of HTML to begin with. Simply using doc.write doesn't solve the problem anyway. You still have to call that file w/ doc.write via an external .js or some other way. Having inline doc.writes still makes the patch affect your flash. This is with my testing,anyway. I'm using the FlashOject that is going around becuase it is xhtml, css compliant etc.. and allows for your alt content to get spidered by the search engines.</description>
		<content:encoded><![CDATA[<p>We are going back to W3C standards as Object and Embed were never part of HTML to begin with. Simply using doc.write doesn&#8217;t solve the problem anyway. You still have to call that file w/ doc.write via an external .js or some other way. Having inline doc.writes still makes the patch affect your flash. This is with my testing,anyway. I&#8217;m using the FlashOject that is going around becuase it is xhtml, css compliant etc.. and allows for your alt content to get spidered by the search engines.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
