[jira] Commented: (TAP5-869) When Submit is used inside Loop and configured as defered (default), context value from last loop iteration is always taken as "selected" event argument

["Torsten Krüger (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAP5-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800165#action_12800165 ] 

Torsten Krüger commented on TAP5-869:
-------------------------------------

When Submit is used inside Grid, context value from last loop iteration is always taken as "selected" event argument.
In contrast to Loop setting defer="false" does not solve the issue for Grid.
Using eventlink with an encapsulated button instead of submit causes the event to occur twice!


> When Submit is used inside Loop and configured as defered (default), context value from last loop iteration is always taken as "selected" event argument
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-869
>                 URL: https://issues.apache.org/jira/browse/TAP5-869
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Vjeran Marcinko
>
> One of major uses of Submit's "context" parameter is when Submit is used inside Loop to be able to distinguish which button was pressed. 
> Unfortunately, always context value from last loop iteration gets passed via "selected" event argument, making it always look as if last iteration submit was selected. 
> When "defer" parameter is set to false (it's true by default), then everything works fine.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.