[TAPESTRY-1775] Multiple submit buttons inside async form can invoke incorrect listener

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.1.3
• Fix Version/s: 4.1.5
• Component/s: Framework, JavaScript
• Assignee: Andreas Andreou
• Reporter: Andreas Andreou
• Created: 24/Sep/07 06:43
• Updated: 18/Nov/07 17:16
• Resolved: 18/Nov/07 17:16

Description

... this can happen when the updateComponents of the buttons doesnt cover the form.

So, in such a case, when button1 is clicked it sets itself as tapestry.forms.form['Form'].clickedButton
and correctly does the async form submit.
However, the xhr response does NOT include any calls to tapestry.form.registerForm since (as stated)
updateComponents may not really include the whole form. So, what this means is that the old value for
tapestry.forms.form['Form'].clickedButton remains - triggering the associated listener no matter how the
new form is submitted.