<?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: New Clientside Scripts, 3rd Party Scripts added</title>
	<atom:link href="http://clientside.cnet.com/code-snippets/new-clientside-scripts-3rd-party-scripts-added/feed/" rel="self" type="application/rss+xml" />
	<link>http://clientside.cnet.com/code-snippets/new-clientside-scripts-3rd-party-scripts-added/</link>
	<description>Making stuff work on the other side of the request.</description>
	<pubDate>Sun, 12 Oct 2008 12:57:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Aaron N.</title>
		<link>http://clientside.cnet.com/code-snippets/new-clientside-scripts-3rd-party-scripts-added/#comment-17389</link>
		<dc:creator>Aaron N.</dc:creator>
		<pubDate>Mon, 16 Jul 2007 16:04:35 +0000</pubDate>
		<guid isPermaLink="false">http://clientside.cnet.com/code-snippets/new-clientside-scripts-3rd-party-scripts-added/#comment-17389</guid>
		<description>Autocompleter was written by the very talented Harald Kirschner (http://www.digitarald.de). I added it to our library because we wanted to start using it on our tools. I did make a few changes to it (and sent them back to Harald to consider), but he is the principle author. The Overlay solution in this script was authored by him and I didn't want to mess with it.

The problem you are having is because you are instantiating the class before the dom has loaded. Wrap your javascript in a domready function and you shouldn't see the error anymore.</description>
		<content:encoded><![CDATA[<p>Autocompleter was written by the very talented Harald Kirschner (http://www.digitarald.de). I added it to our library because we wanted to start using it on our tools. I did make a few changes to it (and sent them back to Harald to consider), but he is the principle author. The Overlay solution in this script was authored by him and I didn&#8217;t want to mess with it.</p>
<p>The problem you are having is because you are instantiating the class before the dom has loaded. Wrap your javascript in a domready function and you shouldn&#8217;t see the error anymore.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mihai Muntenas</title>
		<link>http://clientside.cnet.com/code-snippets/new-clientside-scripts-3rd-party-scripts-added/#comment-16928</link>
		<dc:creator>Mihai Muntenas</dc:creator>
		<pubDate>Mon, 09 Jul 2007 14:12:43 +0000</pubDate>
		<guid isPermaLink="false">http://clientside.cnet.com/code-snippets/new-clientside-scripts-3rd-party-scripts-added/#comment-16928</guid>
		<description>Hello Aron, this comment is connected both with the autocompleter and with the IE Problem ('operation aborted'). I have the problem with MF IE 7 generated by the Autocompleter script, and i don't seem to figure out what to update in the Autocompleter.js so that i obtain the same result as you did with the IFrameShim. And btw, i don't want to be rude but, if you stressed yourself with the IFrameShim, why is the OverlayFix in Autocompleter necessary - wich basicaly provides the same functionality ?</description>
		<content:encoded><![CDATA[<p>Hello Aron, this comment is connected both with the autocompleter and with the IE Problem (&#8217;operation aborted&#8217;). I have the problem with MF IE 7 generated by the Autocompleter script, and i don&#8217;t seem to figure out what to update in the Autocompleter.js so that i obtain the same result as you did with the IFrameShim. And btw, i don&#8217;t want to be rude but, if you stressed yourself with the IFrameShim, why is the OverlayFix in Autocompleter necessary - wich basicaly provides the same functionality ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
