Tapestry
  1. Tapestry
  2. TAPESTRY-1313

css classes fieldMissing/fieldInvalid not written in default ValidationDelegate

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 4.1.2
    • Fix Version/s: 4.1.2
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      any

      Description

      The client side validation api now relies on decorating fields with the specific css class names "fieldMissing" and "fieldInvalid". The ValidationDelegate should append these class names directly onto fields in error so that server side validation looks the same as client side.

        Activity

        Jesse Kuhnert created issue -
        Jesse Kuhnert made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Mark Thomas made changes -
        Workflow jira [ 12398615 ] Default workflow, editable Closed status [ 12568148 ]
        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12568148 ] jira [ 12591236 ]

          People

          • Assignee:
            Jesse Kuhnert
            Reporter:
            Jesse Kuhnert
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development