<?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: IE changes, what to do next?</title>
	<atom:link href="http://www.peterelst.com/blog/2003/10/08/ie-changes-what-to-do-next/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.peterelst.com/blog/2003/10/08/ie-changes-what-to-do-next/</link>
	<description>Flash Platform Geek</description>
	<lastBuildDate>Wed, 04 Jan 2012 21:31:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Shock</title>
		<link>http://www.peterelst.com/blog/2003/10/08/ie-changes-what-to-do-next/comment-page-1/#comment-31</link>
		<dc:creator>Shock</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=20#comment-31</guid>
		<description>http://www.quasimondo.com/eolator.php</description>
		<content:encoded><![CDATA[<p><a href="http://www.quasimondo.com/eolator.php" rel="nofollow">http://www.quasimondo.com/eolator.php</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://www.peterelst.com/blog/2003/10/08/ie-changes-what-to-do-next/comment-page-1/#comment-32</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=20#comment-32</guid>
		<description>Thanks for the link! Mario&#039;s solution is a very good one but I personally prefer this method as it keeps things more readable. &lt;br /&gt;
&lt;br /&gt;
If I remember correctly he was having some problems setting the width and height with the escaped characters (his site seems to be down at the moment). I&#039;m also a bit apprehensive if those escaped characters might be filtered out by Microsoft in a next beta update. Very interesting approach though!</description>
		<content:encoded><![CDATA[<p>Thanks for the link! Mario&#8217;s solution is a very good one but I personally prefer this method as it keeps things more readable. </p>
<p>If I remember correctly he was having some problems setting the width and height with the escaped characters (his site seems to be down at the moment). I&#8217;m also a bit apprehensive if those escaped characters might be filtered out by Microsoft in a next beta update. Very interesting approach though!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://www.peterelst.com/blog/2003/10/08/ie-changes-what-to-do-next/comment-page-1/#comment-33</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=20#comment-33</guid>
		<description>What about the version number: #version=7,0,0,0 -- does that matter? Does that determine minimum required plug-in version? If so, maybe that should be a parameter too.</description>
		<content:encoded><![CDATA[<p>What about the version number: #version=7,0,0,0 &#8212; does that matter? Does that determine minimum required plug-in version? If so, maybe that should be a parameter too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://www.peterelst.com/blog/2003/10/08/ie-changes-what-to-do-next/comment-page-1/#comment-34</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=20#comment-34</guid>
		<description>Good find, thanks Simon! I think I&#039;ll add the version number to the params argument.</description>
		<content:encoded><![CDATA[<p>Good find, thanks Simon! I think I&#8217;ll add the version number to the params argument.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mario</title>
		<link>http://www.peterelst.com/blog/2003/10/08/ie-changes-what-to-do-next/comment-page-1/#comment-36</link>
		<dc:creator>Mario</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=20#comment-36</guid>
		<description>Hi Peter,&lt;br /&gt;
&lt;br /&gt;
the reason why I&#039;m urlencoding the whole block is to avoid any conflicts with quotation marks or linebreaks. As I&#039;m putting the whole OBJECT block into one string this makes any further checks obsolete. The reason is not to obfuscate the code - I only want to avoid introducing any errors into the existing OBJECT.</description>
		<content:encoded><![CDATA[<p>Hi Peter,</p>
<p>the reason why I&#8217;m urlencoding the whole block is to avoid any conflicts with quotation marks or linebreaks. As I&#8217;m putting the whole OBJECT block into one string this makes any further checks obsolete. The reason is not to obfuscate the code &#8211; I only want to avoid introducing any errors into the existing OBJECT.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

