<?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: Another blindingly obvious way to disable a submit button when pressed</title>
	<atom:link href="http://www.sciwerks.com/blog/2006/10/08/another-blindingly-obvious-way-to-disable-a-submit-button-when-pressed/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sciwerks.com/blog/2006/10/08/another-blindingly-obvious-way-to-disable-a-submit-button-when-pressed/</link>
	<description>Software for scientists, by scientists</description>
	<lastBuildDate>Thu, 19 Aug 2010 22:43:31 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andre Pankratz</title>
		<link>http://www.sciwerks.com/blog/2006/10/08/another-blindingly-obvious-way-to-disable-a-submit-button-when-pressed/comment-page-1/#comment-102</link>
		<dc:creator>Andre Pankratz</dc:creator>
		<pubDate>Tue, 21 Nov 2006 17:39:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.sciwerks.com/blog/2006/10/08/another-blindingly-obvious-way-to-disable-a-submit-button-when-pressed/#comment-102</guid>
		<description>Even more obvious would be &quot;this.disabled=true;&quot; ;-)
But this &quot;disabled&quot; solution may prevent the form being submitted in Safari. (Maybe my Safari has a bad day today?)

:disable_with =&gt; &quot;Processing...&quot; works like a breeze!</description>
		<content:encoded><![CDATA[<p>Even more obvious would be &#8220;this.disabled=true;&#8221; ;-)<br />
But this &#8220;disabled&#8221; solution may prevent the form being submitted in Safari. (Maybe my Safari has a bad day today?)</p>
<p>:disable_with =&gt; &#8220;Processing&#8230;&#8221; works like a breeze!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Olbrich</title>
		<link>http://www.sciwerks.com/blog/2006/10/08/another-blindingly-obvious-way-to-disable-a-submit-button-when-pressed/comment-page-1/#comment-68</link>
		<dc:creator>Kevin Olbrich</dc:creator>
		<pubDate>Wed, 18 Oct 2006 02:12:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.sciwerks.com/blog/2006/10/08/another-blindingly-obvious-way-to-disable-a-submit-button-when-pressed/#comment-68</guid>
		<description>True enough.  You may really need a belt AND suspenders for this one.  There are also some subtle side effects of this method.  Notably, it becomes very difficult to determine which button was pressed if you have more than one.</description>
		<content:encoded><![CDATA[<p>True enough.  You may really need a belt AND suspenders for this one.  There are also some subtle side effects of this method.  Notably, it becomes very difficult to determine which button was pressed if you have more than one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Teare</title>
		<link>http://www.sciwerks.com/blog/2006/10/08/another-blindingly-obvious-way-to-disable-a-submit-button-when-pressed/comment-page-1/#comment-67</link>
		<dc:creator>Dave Teare</dc:creator>
		<pubDate>Tue, 17 Oct 2006 23:44:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.sciwerks.com/blog/2006/10/08/another-blindingly-obvious-way-to-disable-a-submit-button-when-pressed/#comment-67</guid>
		<description>This is certainly a hell of a lot better than an alert box saying &quot;Please, for the love of God, don&#039;t press submit twice!&quot;.

However, it needs to be said that one should not rely on JavaScript to solve the double submit problem.  You really need some server-side smarts to detect replays since the user could reload the page and resubmit the form.</description>
		<content:encoded><![CDATA[<p>This is certainly a hell of a lot better than an alert box saying &#8220;Please, for the love of God, don&#8217;t press submit twice!&#8221;.</p>
<p>However, it needs to be said that one should not rely on JavaScript to solve the double submit problem.  You really need some server-side smarts to detect replays since the user could reload the page and resubmit the form.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benjamin</title>
		<link>http://www.sciwerks.com/blog/2006/10/08/another-blindingly-obvious-way-to-disable-a-submit-button-when-pressed/comment-page-1/#comment-64</link>
		<dc:creator>Benjamin</dc:creator>
		<pubDate>Fri, 13 Oct 2006 19:50:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.sciwerks.com/blog/2006/10/08/another-blindingly-obvious-way-to-disable-a-submit-button-when-pressed/#comment-64</guid>
		<description>I also use button disabling but what about the already built in :disable_with =&gt; &quot;Disabling&quot;

Hit me up on AIM btw Kevin yUncleD</description>
		<content:encoded><![CDATA[<p>I also use button disabling but what about the already built in :disable_with =&gt; &#8220;Disabling&#8221;</p>
<p>Hit me up on AIM btw Kevin yUncleD</p>
]]></content:encoded>
	</item>
</channel>
</rss>
