You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Andreas Andreou (JIRA)" <de...@tapestry.apache.org> on 2007/11/18 18:17:44 UTC
[jira] Resolved: (TAPESTRY-1775) Multiple submit buttons inside
async form can invoke incorrect listener
[ https://issues.apache.org/jira/browse/TAPESTRY-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Andreou resolved TAPESTRY-1775.
---------------------------------------
Resolution: Fixed
Francesco, I'm not sure if the case you commented is 100% the same as that of this issue.
The fix should probably handle it, but if you still have issues, reopen + attach something like
https://svn.apache.org/repos/asf/tapestry/tapestry4/trunk/tapestry-framework/src/test-data/app1/
https://svn.apache.org/repos/asf/tapestry/tapestry4/trunk/tapestry-framework/src/test/org/apache/tapestry/integration/app1/pages/
Thx.
> Multiple submit buttons inside async form can invoke incorrect listener
> -----------------------------------------------------------------------
>
> Key: TAPESTRY-1775
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1775
> Project: Tapestry
> Issue Type: Bug
> Components: Framework, JavaScript
> Affects Versions: 4.1.3
> Reporter: Andreas Andreou
> Assignee: Andreas Andreou
> Fix For: 4.1.4
>
> Attachments: form.js.diff
>
>
> ... 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org