<?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: DOMContentLoaded and the quick rise of de facto standards</title>
	<atom:link href="http://www.pathf.com/blogs/2007/11/domcontentloade/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pathf.com/blogs/2007/11/domcontentloade/</link>
	<description>Running commentary about agile development, user experience design and Ajax.</description>
	<pubDate>Mon, 01 Dec 2008 21:00:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: matt snider</title>
		<link>http://www.pathf.com/blogs/2007/11/domcontentloade/#comment-242</link>
		<dc:creator>matt snider</dc:creator>
		<pubDate>Wed, 14 Nov 2007 05:20:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=199#comment-242</guid>
		<description>&lt;p&gt;I have found that by moving my JavaScript files to end of my body tag, I no longer need to worry about DOMContentLoaded. Since the browser has already parsed the page, all the proper DOM references have been made available to JavaScript. Also, the page appears to load faster for users, because the rendering doesn't have to wait on the downloading/processing of JavaScript files.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>I have found that by moving my JavaScript files to end of my body tag, I no longer need to worry about DOMContentLoaded. Since the browser has already parsed the page, all the proper DOM references have been made available to JavaScript. Also, the page appears to load faster for users, because the rendering doesn&#8217;t have to wait on the downloading/processing of JavaScript files.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
