Form_builder expects your theme to render the submit button as input[type=submit]. If your theme (ex: Bootstrap) renders the submit button as button[type=submit] the changes to the form will not be saved.

The use of button[type=submit] instead of input[type=submit] allow the developer a great opportunity to style the button to their needs.

CommentFileSizeAuthor
#5 form_builder-2581153-4-7.x-1.x-dev.patch792 bytesSpartyDan
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

ybabel created an issue. See original summary.

ybabel’s picture

Issue summary: View changes
torotil’s picture

Status: Active » Postponed (maintainer needs more info)

Is this still an issue with the newest release 7.x-1.15?

torotil’s picture

Status: Postponed (maintainer needs more info) » Closed (outdated)
SpartyDan’s picture

Issue summary: View changes
Status: Closed (outdated) » Needs review
FileSize
792 bytes

Form_builder expects your theme to render the submit button as input[type=submit]. If your theme (ex: Bootstrap) renders the submit button as button[type=submit] the changes to the form will not be saved. The attached patch adds #form-builder-positions button[type=submit] to the javascript selector and fixes the issue.

The use of button allows for more styling options than does input.

torotil’s picture

Status: Needs review » Fixed

I've committed a patch like the last one (I simply removed the element selector instead of duplicating it) to 7.x-1.x.

  • torotil committed 275332e on 7.x-1.x
    Issue #2581153 by SpartyDan, ybabel, torotil: webform component position...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.