This is, or is not exactly a bug, depends how you see it.

I have changed from the table Form Style to a pure div/css style.

The biggest problem so far is with Radio Button. That's because every option of a Radio Button is threated as full form control.

Here is a screen a screenshot to show a problem, look at the distance of the Radio Button.



One way to avoid this would be to spit all the related Radio buttons with the same id in the same {field} iteration, instead of having one iteration for each radio option.

Doing so, still have a issue on how to separate it. Do I want it side by side? or Do I want it separated by a <br />? So, something like a {radioseparator} would be handy. (I personally prefer the <br /> option if not possible to choose).

This issue cannot be resolved thru a simple css hack, because I can only differentiate the radio (input) itself thru a class/id in the "additional attribute" option. I cant select the parent element to move it up without a javascript hack. In this particular case, having a {formid} available that could be used as a class to the parent element would help.

So, isn't the radio button problem an issue to anyone else?

Or am I missing something here?

-rsd

A dirty hack(while i am working for a solution on this)

Try adding to your first radio title:

<div id="radios">My title

and to your last radio description </div>

It's not so great but should work. Let me know.

Try adding to your first radio title:
<div id="radios">My title
and to your last radio description </div>


This might break tags structure, closing an outer tag before closing the inner one.

Here is what I have:

Code:

<div style="padding-top: 0.5em">   <div style="float: right; width: 285px; ">     <div style="color: #959BAA; height: 1.5em;">       {fielddesc}     </div>     {field}   </div>   <label class="left"       style="color:#000033;      padding-top: 1em">     {fieldtitle}     <span style="color:         red;">{validationsign}</span>   </label> </div>

So, the tags would break.

I am not in a hurry for this fix. I just wanted to acknowledge it first. So far select boxes are enough for me.

Note that having a {fieldid} that could be used as a class in the parent element (div in my case) would help solve the problem (as hack, but).

-rsd