Hidden fields not quite hidden

[Ask Bjørn Hansen]

Hi,

I'm upgrading to 0.40xx to get Bootstrap rendering (yay).

One small issue I am running into is that with the old Table rendering a "hidden" field got rendered as just the input element, but with Bootstrap rendering they get rendered with the control-group and thus end just leaving some white-space.  Is this intentional?   Am I supposed to fix it with CSS?  I was hoping to do less hacks on the rendering than I did before. :-)

These are my fields:

has_field 'lat' => ( type => 'Hidden', writeonly => 1);

has_field 'lon' => ( type => 'Hidden', writeonly => 1);

has_field 'geocode' => ( type => 'Hidden', writeonly => 1);

and this is the output:

<div class="control-group">
<input type="hidden" name="job.lat" id="job.lat" value="" />
</div>
<div class="control-group">
<input type="hidden" name="job.lon" id="job.lon" value="" />
</div>
<div class="control-group">
<input type="hidden" name="job.geocode" id="job.geocode" value="" />
</div>

Ask

[Patrick Meidl]

On Wed, May 02 2012, Ask Bjørn Hansen <a...@develooper.com> wrote:

> One small issue I am running into is that with the old Table rendering a
> "hidden" field got rendered as just the input element, but with Bootstrap
> rendering they get rendered with the control-group and thus end just
> leaving some white-space. Is this intentional? Am I supposed to fix it
> with CSS? I was hoping to do less hacks on the rendering than I did
> before. :-)
>
> These are my fields:
>
> has_field 'lat' => ( type => 'Hidden', writeonly => 1);

adding

widget_wrapper => 'none'

should solve this issue.

HTH

patrick

--
Patrick Meidl ........................ +43 1 9688226 (home)
Pazmanitengasse 4/10 ................. +43 680 2072780 (mobile)
1020 Wien ............................ pat...@pantheon.at
Austria .............................. http://pmeidl.homelinux.net/
--

[Ask Bjørn Hansen]

On May 2, 2012, at 3:58, Patrick Meidl wrote:

>> has_field 'lat' => ( type => 'Hidden', writeonly => 1);
>
> adding
>
> widget_wrapper => 'none'
>
> should solve this issue.

Indeed, thank you!


Ask