Tapestry
  1. Tapestry
  2. TAPESTRY-2052

Disabled fields still perfom client side validation

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.8
    • Fix Version/s: 5.0.10
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      When disabling Fields (eg. TextField) by setting disabled=true to use them as displaying only components, those components still perform client side validation and show error messages

        Issue Links

          Activity

          Hide
          Howard M. Lewis Ship added a comment -

          It makes sense to set up the validation on the client side, because they could be dynamically re-enabled, but a check for whether the field is disabled should occur on the client side.

          Show
          Howard M. Lewis Ship added a comment - It makes sense to set up the validation on the client side, because they could be dynamically re-enabled, but a check for whether the field is disabled should occur on the client side.

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development