[
https://issues.apache.org/jira/browse/TAPESTRY-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617204#action_12617204 ]
Stéphane Decleire commented on TAPESTRY-2505:
---------------------------------------------
I think it's a complement to the TAPESTRY-2324 issue since the first case described in this issue and set as 'working' does not work either.
> "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
>
> 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@...
For additional commands, e-mail:
dev-help@...