[
https://issues.apache.org/jira/browse/TAP5-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800411#action_12800411
]
Leonard Lu commented on TAP5-869:
---------------------------------
Should other searchers stumble on this ticket, there's a component in the
Tapestry5 wiki that works around this issue:
http://wiki.apache.org/tapestry/Tapestry5SubmitContextComponent
> 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.
