Home » Did you know » Panel DefaultButton does not work

Panel DefaultButton does not work

misc_vol2_051 Or, at least, it didn’t. Here’s what happened:

Yesterday a client asked me to help track down a problem he was having with setting the default button for a text box.

As you should already know, you can make ASP.NET automatically click a specific button on the page (Button, ImageButton, or LinkButton) by grouping everything in a Panel and setting the DefaultButton property to the ID of the button you want to have automatically clicked.

Of course, in situations like these, you can pull your hair out trying to find the problem. There was nothing obviously wrong with the code. Everything was grouped into a panel. All of the Panels had their DefaultButton properties set to the correct button.

Maybe it’s because it is an ImageButton? No, not only are ImageButtons supported, but creating a quick demo verified that they did in fact work.

But what’s this? When I put the ASCX file into design view, it does not render the panel with more than a 1px high rectangle. That’s odd… wonder why it’s doing that. Let’s try resizing it. Nope. That doesn’t work.

And then I looked closer.

All of the code basically looked something like this:

  <asp:Panel DefaultButton="m_ibKeyIngredient"
      runat="server" Width="370px">
    <td valign="top">
      <asp:TextBox ID="m_tbKeyIngredient"
      <asp:ImageButton ID="m_ibKeyIngredient"
        ImageAlign="AbsBottom" />

If you casually read over this code, you completely miss the fact that the TD elements are INSIDE of the Panel. You see the TR element and the panel and if you aren’t thinking clearly, you think the TR element is the cell when in fact, it is the row. The TD elements that represent the cell are further in and easy to miss.

You need to keep in mind that the Panel renders itself as a DIV and you can’t have a DIV tag inside a TR tag.

It turns out that swapping the Panel tag with the TD element solved the whole problem. Unfortunately, this took us several hours of frustration to figure out.

So, what did we learn?

  1. If your ASP.NET client side code isn’t working as you’d expect, validate your HTML.
  2. When working on a problem, if you see another problem that is part of the same code, it is not always inappropriate to take a detour to try to fix that problem. It may in fact fix the problem you are working on. If nothing else, it will give your mind a break.

Related Post

  • DotNetNuke Modules – Creating Base ModulesDotNetNuke Modules – Creating Base Modules Now that we have DotNetNuke installed into Visual Studio we can go ahead and create our first modules. Actually, creating the modules is pretty simple. But it is even easier to do it […]
  • Finding a CSS Class DefinitionFinding a CSS Class Definition A couple of weeks ago I pointed out that you could easily find the definition of a property, method, variable, or class by right-clicking the item and selecting, "Go To Definition" from […]
  • Two CSS Files When Using ASP.NET Themes?Two CSS Files When Using ASP.NET Themes? One of the projects that I'm working on is for a company targeting the Canadian marketplace.  These sites have to be written in both French and English for that country, which means there […]
  • ASP.NET AJAX using JSON – Here’s how.ASP.NET AJAX using JSON – Here’s how. Last week I wrote a post about how simple JSON is. In it I explained the main differences between using JSON and using the update panel. I really started out thinking I'd get to how to […]
  • Advantages of Using Class DiagramAdvantages of Using Class Diagram One of the new tools that showed up in Visual Studio 2005 that I don't see many people taking much advantage of is the Class Diagram.The class diagram displays the classes you drag […]

About Dave Bush

Dave Bush is a Full Stack ASP.NET developer focusing on ASP.NET, C#, Node.js, JavaScript, HTML, CSS, BootStrap, and Angular.JS.Does your team need additional help in any of the above? Contact Dave today.