<?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/"
		>
<channel>
	<title>Comments on: Capturing AutoFill as a Change Event</title>
	<atom:link href="http://furrybrains.com/2009/01/02/capturing-autofill-as-a-change-event/feed/" rel="self" type="application/rss+xml" />
	<link>http://furrybrains.com/2009/01/02/capturing-autofill-as-a-change-event/</link>
	<description>The Furry Brains blog tackles a wide range of issues related to web development and design.</description>
	<lastBuildDate>Tue, 10 May 2011 10:05:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Eugen</title>
		<link>http://furrybrains.com/2009/01/02/capturing-autofill-as-a-change-event/comment-page-1/#comment-40</link>
		<dc:creator>Eugen</dc:creator>
		<pubDate>Wed, 23 Mar 2011 17:12:32 +0000</pubDate>
		<guid isPermaLink="false">http://furrybrains.com/?p=104#comment-40</guid>
		<description>If you don&#039;t want all inputs on the form to be affected, you can write something like this:
&lt;code&gt;
  $(&quot;p.gray input&quot;).listenForChange();
&lt;/code&gt;
After this the only thing you need is to change listenForChange() function not to parse all inputs on the form. This can really mess thing up for you.

So instead of 
&lt;code&gt;
  jquery_object.filter(&quot;:input&quot;).add(&quot;:input&quot;, jquery_object).focus(
&lt;/code&gt;
you should have just
&lt;code&gt;
  jquery_object.focus(
&lt;/code&gt;
as this jquery_object already contains filtered inputs you need.</description>
		<content:encoded><![CDATA[<p>If you don&#8217;t want all inputs on the form to be affected, you can write something like this:<br />
<code><br />
  $("p.gray input").listenForChange();<br />
</code><br />
After this the only thing you need is to change listenForChange() function not to parse all inputs on the form. This can really mess thing up for you.</p>
<p>So instead of<br />
<code><br />
  jquery_object.filter(":input").add(":input", jquery_object).focus(<br />
</code><br />
you should have just<br />
<code><br />
  jquery_object.focus(<br />
</code><br />
as this jquery_object already contains filtered inputs you need.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://furrybrains.com/2009/01/02/capturing-autofill-as-a-change-event/comment-page-1/#comment-39</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Wed, 02 Feb 2011 08:11:58 +0000</pubDate>
		<guid isPermaLink="false">http://furrybrains.com/?p=104#comment-39</guid>
		<description>Thank you!

I had a single input-box form, so I commented out lines 28-31.
Works a treat!

Cheers,

  Andrew.</description>
		<content:encoded><![CDATA[<p>Thank you!</p>
<p>I had a single input-box form, so I commented out lines 28-31.<br />
Works a treat!</p>
<p>Cheers,</p>
<p>  Andrew.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill</title>
		<link>http://furrybrains.com/2009/01/02/capturing-autofill-as-a-change-event/comment-page-1/#comment-37</link>
		<dc:creator>Bill</dc:creator>
		<pubDate>Tue, 07 Sep 2010 19:57:06 +0000</pubDate>
		<guid isPermaLink="false">http://furrybrains.com/?p=104#comment-37</guid>
		<description>Thanks for the help; great idea.

@Glenn

You could add

   &lt;code&gt;clearInterval(intervalID);&lt;/code&gt;

at the end of the jquery filter. That way, once something has changed (auto-fill) it would stop listening.</description>
		<content:encoded><![CDATA[<p>Thanks for the help; great idea.</p>
<p>@Glenn</p>
<p>You could add</p>
<p>   <code>clearInterval(intervalID);</code></p>
<p>at the end of the jquery filter. That way, once something has changed (auto-fill) it would stop listening.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glenn</title>
		<link>http://furrybrains.com/2009/01/02/capturing-autofill-as-a-change-event/comment-page-1/#comment-32</link>
		<dc:creator>Glenn</dc:creator>
		<pubDate>Mon, 14 Jun 2010 12:33:42 +0000</pubDate>
		<guid isPermaLink="false">http://furrybrains.com/?p=104#comment-32</guid>
		<description>Good solution,  but doesn&#039;t this make the browser work a lot harder?  Is there any discernable additional CPU activity when this script is used?

This can be a real problem for mobile devices or where there&#039;s a lot of browser windows &amp; tabs open.</description>
		<content:encoded><![CDATA[<p>Good solution,  but doesn&#8217;t this make the browser work a lot harder?  Is there any discernable additional CPU activity when this script is used?</p>
<p>This can be a real problem for mobile devices or where there&#8217;s a lot of browser windows &amp; tabs open.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Corey</title>
		<link>http://furrybrains.com/2009/01/02/capturing-autofill-as-a-change-event/comment-page-1/#comment-25</link>
		<dc:creator>Corey</dc:creator>
		<pubDate>Mon, 28 Sep 2009 21:48:13 +0000</pubDate>
		<guid isPermaLink="false">http://furrybrains.com/?p=104#comment-25</guid>
		<description>Thank you!  Works well with Douglas Neiner&#039;s in-field labels plugin.

I decided to disable the check for a field being focused.  This solved the problem of the label remaining visible after pasting text using the context menu or when dragged.</description>
		<content:encoded><![CDATA[<p>Thank you!  Works well with Douglas Neiner&#8217;s in-field labels plugin.</p>
<p>I decided to disable the check for a field being focused.  This solved the problem of the label remaining visible after pasting text using the context menu or when dragged.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

