How to Visually Break-up or Wrap a very big Configurable list

I'm creating a form and a large part of it is a configurable list widget.  The information in which I need to collect for one item is quite a lot.  Thusly, it is causing the width of my form to be unmanageable.  Is there a way I can break-up or wrap the configurable list so my form doesn't need to be 2275px-wide? I want the form to fit on the screen better without a lot scrolling. Maybe there is a better template I should to try to accomplish what I doing maybe?     I have attached a screenshot of what I am hoping to accomplish.  The important factor is I cannot break up the configurable list because all the information is for one item.

 

Here's the location of my form: http://form.jotform.us/form/50065349354152? Thank you in advance.

Please take a look at this cloned version of your form: http://form.jotformpro.com/form/50346345687967

I've reduced the width of the text areas, checkboxes and radio buttons and was able to reduce the full width of the form to 1560px.

Would that be a viable solution for you? If it is, feel free to clone that form to your account to check it further.

Unfortunately, the configurable list is rendered using a table. Thus, it would be very complicated to break it into two lines using CSS.

Unfortunately, this is not possible because as I mentioned before the configurable list is rendered in a table and creates a new row every time the add button is clicked. On this case, your would need to use the full source code of your form and modify the behavior of the widget using a script similar to the one mentioned here: http://www.mredkj.com/tutorials/tableaddcolumn.html so you can add columns instead of rows when the add button is clicked.

Let us know if you have further questions.
Thanks.

@ERBArmstrong

We will handle your question on this thread http://www.jotform.com/answers/739447. Thanks!

Please, Tell me more about ERBArmstrong solution. How can I Implement that in my form?

digimarketingcolombia 

This feature is no yet implemented, however a ticket with this request was opened. Feature request are not highly prioritized so we cannot give you an ETA for when this will implemented.