[PatternFly] Validating on each keystroke

Suzanne Hillman wispfox at gmail.com
Fri Jun 30 19:59:59 UTC 2017


In my experience, this is a somewhat complicated thing:

Sometimes people like having feedback before they submit a form. Having it
check when you leave a field is the most common way to handle this that
I've seen, and it's hard to think of a better way to implement this while
still allowing feedback pre-submission. Certainly, having it check _while_
you are typing is a terrible idea for precisely the reason you (and the
link you included) suggest.

If people don't want to have feedback before submission - say, if it's a
check to see if a username is already taken - then there is no concern
about early feedback. The reason, BTW, for not checking on usernames before
submit is that it can be too easy to get a list of existing usernames if it
automatically checks.

I am intrigued by the idea of validating during typing in the case of a
field that had an error in it, though. I can see the appeal, since it means
that you stop having an error as soon as possible, and know when your
original error is resolved. I'm not sure if it should only be validating
based on the original error, or based on all possible errors in that field,
though!

Suzanne

On Fri, Jun 30, 2017 at 1:23 PM, Alexandre Briani Kieling <
abrianik at redhat.com> wrote:

> Hi Sam,
>
> My bad. I didn't notice the validation on each keystroke only happens the
> second time you focus the input boxes.
> It's the first time I see such strategy.
> I like the "Reward early, punish late." strategy mentioned in the article
> I added to the end of my previous message.
> I'd love to know what the UX specialists think about it.
>
> Alexandre
>
> On Fri, Jun 30, 2017 at 9:14 AM, Sam Padgett <spadgett at redhat.com> wrote:
>
>> Hi, Alexandre. While still not ideal, OpenShift doesn't show this error
>> message until the input has lost focus at least once. So if you just start
>> typing without leaving the field, you won't see the error.
>>
>> I'm definitely interested in how we can improve this, though.
>>
>> Sam
>>
>>
>>
>> On Thu, Jun 29, 2017 at 7:13 PM, Alexandre Briani Kieling <
>> abrianik at redhat.com> wrote:
>>
>>> Hi,
>>>
>>> This one is for everyone interested in UX.
>>>
>>> I noticed that the form to create a new project on OpenShift validates
>>> on each keystroke.
>>> I understand that it's good to inform the users about the correctness of
>>> the inputted data as soon as possible but I think it's not being applied
>>> well in this case.
>>> For example, one of the validations is that the project name must have
>>> at least two characters. When the user enters the first letter of his
>>> project name, an error message is presented. The user hasn't finished
>>> entering the project name.
>>>
>>>
>>>
>>>>>> The Inline Validation section of the following article discusses exactly
>>> this problem. It's a good read.
>>> https://blogs.adobe.com/creativecloud/designing-more-efficie
>>> nt-forms-structure-inputs-labels-and-actions/
>>>
>>> What do you think?
>>>
>>>
>>> --
>>> Alexandre KielingSr. Software Engineer, MiddlewareRed Hat
>>>
>>> _______________________________________________
>>> PatternFly mailing list
>>> PatternFly at redhat.com
>>> https://www.redhat.com/mailman/listinfo/patternfly
>>>
>>>
>>
>
>
> --
> Alexandre KielingSr. Software Engineer, MiddlewareRed Hat
>
> _______________________________________________
> PatternFly mailing list
> PatternFly at redhat.com
> https://www.redhat.com/mailman/listinfo/patternfly
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/patternfly/attachments/20170630/cd0a6a7e/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openshift-new-project.png
Type: image/png
Size: 22859 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/patternfly/attachments/20170630/cd0a6a7e/attachment.png>


More information about the PatternFly mailing list