Form Builder inserting incomplete code for a legend...

I found that after creating a form using FB, the fieldset was smaller than the contents of the actual fieldset so the 1px border I turned on would show where the fieldset was supposed to be, but the form elements (such as first name, last name, etc.) were outside of the fieldset's border. The legend also wasn't appearing correctly. The form elements were breaking out of the top of the fieldset so I wouldn't see a border for the top of the fieldset, just the sides and the bottom.

Just for grins, I decided to turn off the legend and things looked OK. So I looked at the code for the legend and discovered that FB had created the following code:

<legend class="groupHeader">
Tell us about yourself <span class=</legend>

No idea why the <span class= code is being inserted, but it is the culprit for screwing up the fieldset as well as the legend.

I removed the code by hand for all the legends (they all had the same errant code inserted) and the form looked OK. Then I decided to try and edit the form and change the form's width. After doing this and clicking Finish, I could see where FB was generating code for the form, but it reinserted the errant <span class= code for each legend again.

Any idea what's causing this?

steve

I just created a form using Form Builder and I wasn't able to reproduce this error. Can you be more descriptive about what content you added to the form when creating it?

Do you have anything else applied to the page? Server behaviors or other WebAssist products?

Nope, no other behaviors have been added and I'm not using any other extensions for this page. I stripped out everything that I had around spry effects from my original page, made sure there was absolutely no Java Script or anything else with the page, deleted my existing form (used during creation under DW CS4) and built a form from scratch using FB.

Perhaps I should try uninstalling the extension and reinstalling it?

steve

I tried uninstalling FB and then reinstalling it based on the current download for the extension. If I attempt to Edit the Design, as soon as it displays the form it shows the fieldsets jacked up. If I cancel, it doesn't overwrite the errant code that I removed, but if I click finish, the code is once again inserted. This is without doing anything other than clicking on Edit Design and then clicking Finish. So something is going on right at the beginning.

Are some files opened during Edit Design that I don't know about that could have this coding problem embedded in them?

If I click ignore legend, the problem goes away (because the errant "<span class=" code is not inserted) in the legend tag as described in the original post.

steve

Do you have the Use <span> instead of <legend> checkbox checked when you specify the settings for the legend?

There shouldn't be any files that are opened that would cause this issue.

Does this happen when you choose both other options for the legend (show legend in fieldset and Show in label header)?

Also did you choose a preset form/design type and edit from there or start from blank and made your own changes?

OK Jimmy, I found the problem. I believe that I started with a preset form and design type. After I initially changed some of the fields and names that were in the preset, I also added some of my own lines and sets to create a form. After that, I kept using Edit Design to change the layout.

What I didn't do was use Edit Form since I was trying to muck with the layout so it would fit in my page correctly. Had I gone to Edit Form, I would have discovered that the "Label" for each fieldset (which is really the Legend) had this extraneous code in it.

So a label for a fieldset read "Tell us about yourself <class=". Another fieldset's label read "Contact information <class=" and the last fieldset had the label of "Security info <class=" . Since I hadn't been using the Edit Form feature, I never noticed this extra code in each of the labels (legends). I have no idea where it came from, but this is what was causing the problem.

Thanks for your suggestions and hopefully someone else doesn't run in to this problem (or if they do, they find this post).

steve

Glad to know that you figured it out. That was one of the next suggestions I was going to have you check, but its a good thing that you're proactively checking these things as well. If you have any additional issues, feel free to make a new thread.