Tapestry 5
  1. Tapestry 5
  2. TAP5-1892

FormFragment validates non-displayed fragments (reopen)

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.2.1, 5.2.3
    • Fix Version/s: 5.4
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      (The Issue TAP5-410 is closed, I cannot reopen it)

      Fields in FormFragments still get validated when using IE7.

      Testcase:

        Issue Links

          Activity

          Hide
          Carsten Maneg added a comment -

          Any activity on this issue?
          Problem with IE 8 as well and affects version 5.3.4 (of course).

          Show
          Carsten Maneg added a comment - Any activity on this issue? Problem with IE 8 as well and affects version 5.3.4 (of course).
          Hide
          Geoff Callender added a comment -

          I can't recreate this issue. I'm using IE8 with, and without, Compatibility mode. Are there other settings I need to apply?

          Show
          Geoff Callender added a comment - I can't recreate this issue. I'm using IE8 with, and without, Compatibility mode. Are there other settings I need to apply?
          Hide
          Carsten Maneg added a comment -

          Can't tell you exactly. Sorry, no time for testing a plain example.
          Its a production bug (customer app) and I will use a workaround and remove tapestry validation by validate fields manually.

          We are using a quite simple page with form (clientValidation=false) and 3 formfragments.
          Validation is configured with annotation (@Validate) for required fields.
          Even fragment fields are non-displayed they are validated.

          Show
          Carsten Maneg added a comment - Can't tell you exactly. Sorry, no time for testing a plain example. Its a production bug (customer app) and I will use a workaround and remove tapestry validation by validate fields manually. We are using a quite simple page with form (clientValidation=false) and 3 formfragments. Validation is configured with annotation (@Validate) for required fields. Even fragment fields are non-displayed they are validated.
          Hide
          Lenny Primak added a comment -

          Has there been any progress on this issue? I think we are running into it.

          Show
          Lenny Primak added a comment - Has there been any progress on this issue? I think we are running into it.
          Hide
          Howard M. Lewis Ship added a comment -

          This has been addressed as part of the 5.4 rewrite of client-side JavaScript.

          Show
          Howard M. Lewis Ship added a comment - This has been addressed as part of the 5.4 rewrite of client-side JavaScript.

            People

            • Assignee:
              Howard M. Lewis Ship
              Reporter:
              Beat Durrer
            • Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development