Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. 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

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Invalid
    • 5.1.0.5
    • None
    • tapestry-core
    • None

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              vjeran@tis.hr Vjeran Marcinko
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: