Tapestry
  1. Tapestry
  2. TAPESTRY-1942

Client side validation should be triggered when the user moves out of a field

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.6
    • Fix Version/s: 5.0.7
    • Component/s: None
    • Labels:
      None

      Description

      Currently, client side validation occurs only as the user submits the form.

      It would be better if validation occured for individual fields as the user tabs out of them.

      Validation would be re-run at form submit (and of course, again on the server).

      This radically changes the way that input validation errors are displayed; I've been working on a kind of "bubble" that is positioned above the field to contain the error message.

        Activity

        Hide
        Howard M. Lewis Ship added a comment -

        I think that this will be tuned and otherwise revisited in later releases, but what's present is a good first pass.

        Show
        Howard M. Lewis Ship added a comment - I think that this will be tuned and otherwise revisited in later releases, but what's present is a good first pass.
        Hide
        Howard M. Lewis Ship added a comment -

        I've added in Ben Acker's improved bevel image and CSS (the bevel is the balloon-ish popup displaying the error message). This is a good first pass, but it needs a bit of additional work. The current approach is not ideal, it can be cluttered if you submit a form and many fields get a bevel. The idea of dimming the bevels of other fields is not bad, but could be a bit better. The bevels need to re-position themselves when the layout of the component they are attached to changes ... given the other field decoration, perhaps only the field with focus should have it's bevel displayed at all?

        In addition, haven't tested IE support at all, especially IE 6 with its nasty z-order problems.

        Show
        Howard M. Lewis Ship added a comment - I've added in Ben Acker's improved bevel image and CSS (the bevel is the balloon-ish popup displaying the error message). This is a good first pass, but it needs a bit of additional work. The current approach is not ideal, it can be cluttered if you submit a form and many fields get a bevel. The idea of dimming the bevels of other fields is not bad, but could be a bit better. The bevels need to re-position themselves when the layout of the component they are attached to changes ... given the other field decoration, perhaps only the field with focus should have it's bevel displayed at all? In addition, haven't tested IE support at all, especially IE 6 with its nasty z-order problems.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development