I suspect it's tapestry-bootstrap. There is a visitor that changes the html from the Tapestry format to Bootstrap. In the case of forms I believe it wraps each input in a div. My guess is this does not happen on a zone. I suspect you can work around this by added the correct markup inside your zone. Most likely you need a
<div class="form-group> </div> see http://getbootstrap.com/css/#forms If that does not work post the output and perhaps I can figure it out On Monday, January 26, 2015, Stephan Windmüller < stephan.windmuel...@tu-dortmund.de> wrote: > Hello, > > I am using tapestry-bootstrap with a BeanEditForm. For a select field > which should only be displayed after a special event, I added this code: > > > <p:value> > <t:zone t:id="substanceTypeZone" t:visible="show" > t:update="show"> > <t:if test="valueAvailable"> > <t:label for="valueSelect" > class="control-label">Value</t:label> > > <t:select t:id="valueSelect" > value="value" > model="valueModel" > encoder="valueEncoder" > blankOption="ALWAYS" > blankLabel="Please select..."/> > </t:if> > </t:zone> > </p:value> > > > As defined in the zone, it should not be visible if "show" is false. The > logic works perfectly, but the layout is not what I expected. What is > missing is a div with the class "controls" which is added by > tapestry-bootstrap around the select field. Adding it manually to the > TML results in a garbled output when "show" is true, because then two > divs of this type exist. > > Is this a problem with tapestry-bootstrap or my zone? > > - Stephan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > <javascript:;> > For additional commands, e-mail: users-h...@tapestry.apache.org > <javascript:;> > >
