Tapestry
  1. Tapestry
  2. TAPESTRY-2393

The FormFragment component should isolate its action stream (t:formdata hidden field) such that the entire client-side element may be removed

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.11
    • Fix Version/s: 5.0.13
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      FormFragment currently "collects" actions but ultimately embeds them in the form itself. It also uses a hidden form field to control whether the actions for the fragment are executed on the server side.

      An alternative approach would be for the fragment's actions to be stored in its own hidden field. On a form submit, the fragment could remove the element and, thus, no update to the server for those fields and no need to maintain the "enabled/disabled" form field.

      This also has additional applications for use with FormInjector and Ajax forms wherein rows can be easily added and removed from the client-side.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development