{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 The star\" 的问题《IE needs 2 textboxes to submit a button?》','https://www.manongdao.com/q-397174.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I've got this weird problem, and I'm not sure whether ASP.NET or IE 7 is to blame...
The idea is this: When I have just one textbox and one (submit) button on my form, then pressing ENTER while inside the textbox will just POST the textbox'es value. The button does not get submitted and does not trigger the Click even server-side.
When I have two textboxes, then hitting ENTER in any of them will also send the button and trigger the Click event.
WTF?
Added: Seems to be an IE-related issue. Here's a simple example to demonstrate. Pay attention to the address bar and hit ENTER when in the first textbox, and then when in some of the last two.
<html>
<body>
<form method="GET" action="" style="display: block">
<input type="text" id="ctl1" name="ctl1" value="">
<input type="submit" id="ctl2" name="ctl2" value="Klik">
</form>
<form method="GET" action="" style="display: block">
<input type="text" id="ctl1" name="ctl1" value="">
<input type="text" id="ctl3" name="ctl3" value="">
<input type="submit" id="ctl2" name="ctl2" value="Klik">
</form>
</body>
</html>
The default behavior for a html form is to submit the form if any control has focus. What you need to do is trap for the ENTER key and then handle form submissions how you want to.
I have done something like this before (there are many sources for this script):
If you are using asp.net, one option I've used to correct this problem is to set the button to runat="server", wrap your controls in a panel, and set the panel's defaultbutton property to the ID of the button.
If I were you, I would write the form so that you don't need to worry about the click handler on the button (after all, it wasn't clicked), and also ignore the button's value when the form is submitted (never understood why buttons have values that are submitted).
As a comment to your question points out, the ENTER button's behaviour is not well standardized and you can get different behaviour in different browsers, so even if you think your page works properly it might not for all your users. Also, there are other ways forms can be submitted:
<input type="image">For robustness, I'd use the form's onsubmit event handler to do anything that needs to happen when the form is submitted, and only use the onclick handlers to do things that need to happen when a specific button is clicked (most will just submit the form). As for the button value, I'd use an
<input type="hidden">to store whatever hidden value I want for the multiple button scenario, and not bother with the button's value.However, if those options are not available to you, you can add a hidden input field:
This seemed to solve the problem for me on IE8 with your sample code.
If you're using ASP.NET then you should only have a single form. You should also have the runat="server" attribute on any controls you want to access server-side (including the form iteself).OK, no ASP.NET. It's not posting anything because you've got GET as the method in your form??