<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: fun with browsers and javascript</title>
	<link>http://www.digitalramble.com/2006/07/27/61/</link>
	<description>surveyor of the foothills, valleys and occasional sheer cliff drops of the world of computer programming...</description>
	<pubDate>Wed, 07 Jan 2009 05:03:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Brother Erryn</title>
		<link>http://www.digitalramble.com/2006/07/27/61/#comment-67</link>
		<dc:creator>Brother Erryn</dc:creator>
		<pubDate>Tue, 08 Aug 2006 14:27:14 +0000</pubDate>
		<guid>http://www.digitalramble.com/2006/07/27/61/#comment-67</guid>
		<description>Funny seeing this here, as just last night I finally identified and fixed a very similar problem that had been plaguing our game for months. In our case, setting the innerHTML of a SPAN tag to content containing a P tag, closed or not, was blowing JavaScript. Removing the P tag got rid of the error, and changing the SPAN to a DIV solved the problem more permanently. Like you, this only affected IE6 users.</description>
		<content:encoded><![CDATA[<p>Funny seeing this here, as just last night I finally identified and fixed a very similar problem that had been plaguing our game for months. In our case, setting the innerHTML of a SPAN tag to content containing a P tag, closed or not, was blowing JavaScript. Removing the P tag got rid of the error, and changing the SPAN to a DIV solved the problem more permanently. Like you, this only affected IE6 users.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
