Using the Webform Table Element module, I found a bug with Webform upon cloning a fieldset with children. The children of this fieldset in my specific case are a table element, but this issue is most likely prevalent with any cloned element.

1. The cloned fieldset allows there to be two fieldsets with the same "field key" (machine readable key). This renders the cloned table as empty when viewing submissions: <table> </table>
2. The cloned fieldset automates the "weight" to be the same so order is not guaranteed according to where the slider position is. Say I have a fieldset with the weight 25; the clone will have a weight of 25 as well and appear to be positioned above or below, but it really can be the opposite.

Info + Screenshots here:
http://drupal.org/node/1662708#comment-6168408

Comments

ownage’s picture

Issue summary: View changes

More info on #1

ownage’s picture

Version: 7.x-3.9 » 7.x-3.18
quicksketch’s picture

The cloned fieldset allows there to be two fieldsets with the same "field key" (machine readable key).

This is intentional functionality of Webform. You've always been able to use the same field key as long as the fields are under different fieldsets.

The cloned fieldset automates the "weight" to be the same so order is not guaranteed according to where the slider position is.

This is a duplicate of #780700: Component order may be incorrect on cloning components (when components have identical weights).

helmo’s picture

Status: Active » Closed (duplicate)

This seems answered, idle.

helmo’s picture

Issue summary: View changes

More intro info.