Layout: Placing containers within a form..

I have a form panel with a bunch of stuff in it. I'm trying to make a container that will house three buttons and I'm having a hard time getting them to show up. I'm trying to follow the example in the docs for Ext.Container, but no matter what combination of layout vs not vs changing it from a container to a panel, the buttons do not get rendered & I'm not sure why. The rest of the form is rendered just fine and the container below is rendered with a height and width of 0 and no child elements. If I specify a height and width the container will show up with that height and width, but again... No child elements (no buttons).

**update** If I use the html config option I can see the html, but the items array doesn't seem to be working for creating child elements.

Here's the code I have right now for that specific container (posted full code):

The others often require that THEY be sized and actively size their child items.

Table layout does like a table and stretches to accommodate its child items.

Why float:left?

I'm floating this button container next to a textarea (which is also float:left in the x-form-item node). The float is working fine, but even if I take out all of the other items in the form except for this container (as posted above), I get the same results. Specifying layout:"table" in the above code isn't working for me either.

I wondered if that might not work. The short hand usually works in places where the child item type is expected, but I have done some unique things where I had to use the full instantiation. I also noticed that you directly name the div, and rendered your buttons to the div, kind of bypassing the insert or add method on container. Even though this works, there may be some attributes that you expect that may not get set, such as ownerCt.

I wondered if that might not work. The short hand usually works in places where the child item type is expected, but I have done some unique things where I had to use the full instantiation. I also noticed that you directly name the div, and rendered your buttons to the div, kind of bypassing the insert or add method on container. Even though this works, there may be some attributes that you expect that may not get set, such as ownerCt.