<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Unobtrusive Javascript: Introduction</title>
	<atom:link href="http://scottmoonen.com/2008/06/23/unobtrusive-javascript-introduction/feed/" rel="self" type="application/rss+xml" />
	<link>http://scottmoonen.com/2008/06/23/unobtrusive-javascript-introduction/</link>
	<description>Jesu, Juva</description>
	<lastBuildDate>Sat, 21 Jan 2012 20:27:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Unobtrusive Javascript: Self-labeling text inputs &#171; I gotta have my orange juice.</title>
		<link>http://scottmoonen.com/2008/06/23/unobtrusive-javascript-introduction/#comment-334</link>
		<dc:creator><![CDATA[Unobtrusive Javascript: Self-labeling text inputs &#171; I gotta have my orange juice.]]></dc:creator>
		<pubDate>Thu, 01 Oct 2009 12:23:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fullvalence.com/?p=26#comment-334</guid>
		<description><![CDATA[[...] unobtrusive Javascript (see introduction), we can add behavior to a text input element to automatically label it with this sort of help text [...]]]></description>
		<content:encoded><![CDATA[<p>[...] unobtrusive Javascript (see introduction), we can add behavior to a text input element to automatically label it with this sort of help text [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Full Valence &#187; Blog Archive &#187; Unobtrusive Javascript: Self-labeling text inputs</title>
		<link>http://scottmoonen.com/2008/06/23/unobtrusive-javascript-introduction/#comment-110</link>
		<dc:creator><![CDATA[Full Valence &#187; Blog Archive &#187; Unobtrusive Javascript: Self-labeling text inputs]]></dc:creator>
		<pubDate>Fri, 18 Jul 2008 20:28:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fullvalence.com/?p=26#comment-110</guid>
		<description><![CDATA[[...] unobtrusive Javascript (see our earlier introduction), we can add behavior to a text input element to automatically label it with this sort of help text [...]]]></description>
		<content:encoded><![CDATA[<p>[...] unobtrusive Javascript (see our earlier introduction), we can add behavior to a text input element to automatically label it with this sort of help text [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Full Valence &#187; Blog Archive &#187; Unobtrusive Javascript: Expandable textareas</title>
		<link>http://scottmoonen.com/2008/06/23/unobtrusive-javascript-introduction/#comment-109</link>
		<dc:creator><![CDATA[Full Valence &#187; Blog Archive &#187; Unobtrusive Javascript: Expandable textareas]]></dc:creator>
		<pubDate>Tue, 08 Jul 2008 13:58:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fullvalence.com/?p=26#comment-109</guid>
		<description><![CDATA[[...] unobtrusive Javascript (see our earlier introduction), we can add behavior to textareas to make them automatically expand or contract as text is entered [...]]]></description>
		<content:encoded><![CDATA[<p>[...] unobtrusive Javascript (see our earlier introduction), we can add behavior to textareas to make them automatically expand or contract as text is entered [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Moonen</title>
		<link>http://scottmoonen.com/2008/06/23/unobtrusive-javascript-introduction/#comment-108</link>
		<dc:creator><![CDATA[Scott Moonen]]></dc:creator>
		<pubDate>Mon, 23 Jun 2008 16:57:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fullvalence.com/?p=26#comment-108</guid>
		<description><![CDATA[Thanks, Jordan, that&#039;s a good point.  That&#039;s an argument in favor of defining the anchor as a &lt;span&gt; instead and then having the handler replace it with an anchor.]]></description>
		<content:encoded><![CDATA[<p>Thanks, Jordan, that&#8217;s a good point.  That&#8217;s an argument in favor of defining the anchor as a &lt;span&gt; instead and then having the handler replace it with an anchor.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jordan</title>
		<link>http://scottmoonen.com/2008/06/23/unobtrusive-javascript-introduction/#comment-107</link>
		<dc:creator><![CDATA[Jordan]]></dc:creator>
		<pubDate>Mon, 23 Jun 2008 16:46:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fullvalence.com/?p=26#comment-107</guid>
		<description><![CDATA[One thing to remember with this technique is that it works best for small documents. Most of the Javascript techniques to attach event handlers to DOM nodes won&#039;t work until the DOM has been fully loaded, but some browsers will begin to display page content before that point.

If the user clicks on a link that has not had the Javascript handler attached to it yet, they&#039;ll get the default link behavior, whatever that is.

The bigger the document, the greater the chance that the user will be able to interact with the page before the dynamic behavior is in place.]]></description>
		<content:encoded><![CDATA[<p>One thing to remember with this technique is that it works best for small documents. Most of the Javascript techniques to attach event handlers to DOM nodes won&#8217;t work until the DOM has been fully loaded, but some browsers will begin to display page content before that point.</p>
<p>If the user clicks on a link that has not had the Javascript handler attached to it yet, they&#8217;ll get the default link behavior, whatever that is.</p>
<p>The bigger the document, the greater the chance that the user will be able to interact with the page before the dynamic behavior is in place.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

