29 Sep 2009
21 Apr 2010
Link to this post
I suspected the problem was as such. After debugging with FireBug a bit, I figured out the cause, but not the cure.
My SearchBox template included a <asp:TextBox> and <asp:ImageButton>. Both of which, as you know, get translated into <input> tags. The secondary textbox that I was using had both a custom validator and
At any rate, my resolution was just to replace the ImageButton in my template with an Image. Afterwards, the image's click event doesn't propagate incorrectly and things work as expected.
The funniest thing about this issue was that in FireBug, upon inspecting the event object during the ImageButton's erroneously firing click event, the "explicitOriginalTarget" is listed as my secondary textbox. This originally made me think that ASP.NET was assigning a default button, but the
WebForm_FireDefaultButton method was not being called.