Tapestry 5
  1. Tapestry 5
  2. TAP5-1856

Documentation for SubmitMode.CANCEL is out of date w.r.t. new 5.3 form cancel logic

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Invalid
    • Affects Version/s: 5.3, 5.4
    • Fix Version/s: None
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      The documentation for SubmitMode claims that server-side validation still occurs; this was true in 5.2 (SubmitModel.CANCEL was purely a client-side behavior then), but in 5.3, the CANCEL means that server-side validation and other processing is bypassed.

      What's really needed is a third option, perhaps UNCONDITIONAL, meaning to bypass client-side validation, but continue normally on the server-side.

        Issue Links

          Activity

          Howard M. Lewis Ship created issue -
          Howard M. Lewis Ship made changes -
          Field Original Value New Value
          Assignee Howard M. Lewis Ship [ hlship ]
          Howard M. Lewis Ship made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          Howard M. Lewis Ship made changes -
          Status In Progress [ 3 ] Resolved [ 5 ]
          Resolution Invalid [ 6 ]
          Bob Harner made changes -
          Link This issue relates to TAP5-2539 [ TAP5-2539 ]

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development