Uploaded image for project: 'Tapestry'
  1. Tapestry
  2. TAPESTRY-1313

css classes fieldMissing/fieldInvalid not written in default ValidationDelegate

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: 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.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: