You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2008/09/08 19:25:44 UTC
[jira] Closed: (TAPESTRY-2505) "Selected" event of Submit component
is not correctly triggered when the form submission is handled as an Ajax
request
[ https://issues.apache.org/jira/browse/TAPESTRY-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-2505.
------------------------------------------
Resolution: Duplicate
> "Selected" event of Submit component is not correctly triggered when the form submission is handled as an Ajax request
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2505
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2505
> Project: Tapestry
> Issue Type: Bug
> Components: XHR/dhtml/Ajax
> Affects Versions: 5.0.14
> Reporter: Stéphane Decleire
> Assignee: Howard M. Lewis Ship
>
> When a form submission is handled as an Ajax Request and this form includes several submit components, all the "selected" events of those components are the same.
> For example :
> <t:form t:id="testForm" t:zone="testZone">
> <t:textfield t:id="field1" t:value="field1"/>
> <t:submit t:id="submit1" t:value="1"/>
> <t:submit t:id="submit2" t:value="2"/>
> </t:form>
> void onSelectedFromSubmit1() {
> log.info("submit1");
> }
> void onSelectedFromSubmit2() {
> log.info("submit2");
> }
> Every form submited by both submit1 and submit2 components will trigger the onSelectedFromSubmit1 function and the onSelectedFromSubmit2 will never be triggered.
--
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