1. Tapestry
  2. TAPESTRY-1109

Client Form validation validates disabled fields


    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 4.1.1
    • Fix Version/s: 4.1.1
    • Component/s: JavaScript
    • Labels:


      Don't know if this is a bug or a "feature", and it appears to be down in DoJo, perhaps. But required and other field validations on the client side happen even if a field is disabled. Is that what we want? I'd expect that since disabled field data is not sent to the server anyway that validating them is unnecessary.

      The problem is that I have some form fields that are disabled if they are not required, but they are dynamically enabled and thus required based on values of other fields (a select, in particular, where some values require an additional field and others do not). Currently, I have to add my own custom validation profile to check if the fields are disabled first before performing standard validation. That's a bit cumbersome if I repeat the pattern on multiple pages.


        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12567904 ] jira [ 12591031 ]
        Mark Thomas made changes -
        Workflow jira [ 12386221 ] Default workflow, editable Closed status [ 12567904 ]
        Jesse Kuhnert made changes -
        Fix Version/s 4.1.1 [ 12312021 ]
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Jesse Kuhnert made changes -
        Field Original Value New Value
        Assignee Jesse Kuhnert [ jkuhnert ]
        Greg Woolsey created issue -


          • Assignee:
            Jesse Kuhnert
            Greg Woolsey
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created: