<?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: Rediscovering the button element</title>
	<atom:link href="http://yelotofu.com/2007/11/rediscovering-the-button-element/feed/" rel="self" type="application/rss+xml" />
	<link>http://yelotofu.com/2007/11/rediscovering-the-button-element/</link>
	<description>"In building standards compliant sites we are creating a better Web for the future."</description>
	<lastBuildDate>Thu, 11 Mar 2010 17:53:20 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: caphun</title>
		<link>http://yelotofu.com/2007/11/rediscovering-the-button-element/comment-page-1/#comment-910</link>
		<dc:creator>caphun</dc:creator>
		<pubDate>Wed, 12 Dec 2007 13:46:44 +0000</pubDate>
		<guid isPermaLink="false">http://yelotofu.com/2007/11/rediscovering-the-button-element/#comment-910</guid>
		<description>Thanks for the insightful comment. I did not consider backend implications of the &lt;code&gt;button&lt;/code&gt; element whilst writing this post.

I would say however that it&#039;s never a good idea to use the value of a &lt;code&gt;button&lt;/code&gt; or &lt;code&gt;input&lt;/code&gt; element for parsing, so the &lt;code&gt;hidden&lt;/code&gt; element solution is equally valid when using an &lt;code&gt;input&lt;/code&gt; element as a button.

As for the IE6 issue with multiple submit buttons I can only say that IE6 is crap and Microsoft know it!

Love your new site btw. :)</description>
		<content:encoded><![CDATA[<p>Thanks for the insightful comment. I did not consider backend implications of the <code>button</code> element whilst writing this post.</p>
<p>I would say however that it&#8217;s never a good idea to use the value of a <code>button</code> or <code>input</code> element for parsing, so the <code>hidden</code> element solution is equally valid when using an <code>input</code> element as a button.</p>
<p>As for the IE6 issue with multiple submit buttons I can only say that IE6 is crap and Microsoft know it!</p>
<p>Love your new site btw. <img src='http://yelotofu.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Huy Dinh</title>
		<link>http://yelotofu.com/2007/11/rediscovering-the-button-element/comment-page-1/#comment-879</link>
		<dc:creator>Huy Dinh</dc:creator>
		<pubDate>Mon, 10 Dec 2007 14:11:22 +0000</pubDate>
		<guid isPermaLink="false">http://yelotofu.com/2007/11/rediscovering-the-button-element/#comment-879</guid>
		<description>The button element is great, it is fantastic with javascript. It doesn&#039;t quite work in a form though, because Internet Explorer chooses not to follow specification and send the button&#039;s inner HTML instead of it&#039;s value... which is a bit annoying.

My solution to make it work in forms is not to have it send anything, put the information to be sent into hidden input field. That doesn&#039;t solve the problem if you wanted conditional submit buttons though. So if you want multiple submit buttons with different values, you&#039;d have to stick with input buttons.</description>
		<content:encoded><![CDATA[<p>The button element is great, it is fantastic with javascript. It doesn&#8217;t quite work in a form though, because Internet Explorer chooses not to follow specification and send the button&#8217;s inner HTML instead of it&#8217;s value&#8230; which is a bit annoying.</p>
<p>My solution to make it work in forms is not to have it send anything, put the information to be sent into hidden input field. That doesn&#8217;t solve the problem if you wanted conditional submit buttons though. So if you want multiple submit buttons with different values, you&#8217;d have to stick with input buttons.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
