@████████- is this in a table or a collection?

Do you have CSS and/or Javascript altering the appearance of the fields?  If so, can you share that?

Hi Matthew,

It is a collection and below is the CSS and Javascript

css:

.two-per-line {
    Display: inline-block;
    width: 12%;
}

.cf-formwrap {
    margin: 52px auto 40px;
    max-width: 900px;
}

.cf-lab-small .cf-field {
    width: 35%;
     min-width: 413px;
}

#q8 {
    padding: 0px 0px;
}

#q10 {
    padding: 0px 11px;
    padding-right: 114px;
}

li#q9 {
  
    padding-right: 219px;
      width: 73px;
}

li#q12 {
    padding-left: 0px;
    padding-right: 212px;
}

li#q16 {
    padding-left: 1px;

}

.cf-lab-small .label-left .cf-label, .cf-lab-small .label-right .cf-label {
    width: 15%;
  
}
 

javascript:

$(document).ready(function(){
   
  setTimeout(function(){
  $('.totalSeed input').change();
  }, 1000);  
 
});

It does work without the code, but don't like the layout of the form. 

It's going to be part of the CSS, I'm just not completely certain which one it is without being able to examine things.

It might be this one:

.cf-lab-small .cf-field {
    width: 35%;
     min-width: 413px;
}

Because it sets a large minimum width.

The issue is that the active version of the form has some differences from the archived version of the form.  Things like input fields become text, and stuff like that.  For most things, it doesn't matter.  But there are definitely situations where things don't react how you'd expect because of these differences (example, I've had Javascript trigger based on a field value that modifies the appearance, but the archived form doesn't have field values anymore, so the script doesn't work).

Try this: Go to the Monitor page, and find a version of your form that has already been completed.  You can go to the form and see the submitted form.  This will be the same version of the form that gets pushed to the Repository, but unlike the repository version, you can use the browser's inspect function to see what is different about that field than when it shows in the live form (and in there you can actually tweak values to see what makes it look right, without having to go back and make changes to the original and resubmit).

Also - with the way you are trying to lay it out, you might have happier results with a table.  I find that Collections are great when you need each record to have multiple rows or unusual things like custom HTML, but that for something like this, with just 5 records, tables do the same thing but streamline the formatting a lot.

I'll explore that, see if I can pin point it.  Thanks Matt

I just gave you a short example, the actual form has 20 lines and can go much higher but is variable. Would a table still work for this purpose?