<?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: Managing Internet Explorer, JavaScript, and client and offset values returning zero</title>
	<atom:link href="http://www.tommcfarlin.com/2008/06/26/managing-internet-explorer-javascript-and-client-and-offset-values-returning-zero/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tommcfarlin.com/2008/06/26/managing-internet-explorer-javascript-and-client-and-offset-values-returning-zero/</link>
	<description>assorted development tomfoolery</description>
	<pubDate>Sat, 22 Nov 2008 02:36:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Thanks</title>
		<link>http://www.tommcfarlin.com/2008/06/26/managing-internet-explorer-javascript-and-client-and-offset-values-returning-zero/#comment-88</link>
		<dc:creator>Thanks</dc:creator>
		<pubDate>Wed, 23 Jul 2008 13:28:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.tommcfarlin.com/?p=40#comment-88</guid>
		<description>Wow, definitely one of the nastier bugs IE has to offer.

In my case, the JS was in an iframe from a different domain than the parent document. It seems the problem was actually with the parent document readyState, which I couldn't query (methinks).

Finally, I simply queried the value (offsetHeight) directly. Ugly hack, but it's holding, so far.

Thank you for taking the time to post a solution for this infuriatingly obscure bug.</description>
		<content:encoded><![CDATA[<p>Wow, definitely one of the nastier bugs IE has to offer.</p>
<p>In my case, the JS was in an iframe from a different domain than the parent document. It seems the problem was actually with the parent document readyState, which I couldn&#8217;t query (methinks).</p>
<p>Finally, I simply queried the value (offsetHeight) directly. Ugly hack, but it&#8217;s holding, so far.</p>
<p>Thank you for taking the time to post a solution for this infuriatingly obscure bug.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.294 seconds -->
