Kevin, I'm 
re-posting https://docs.angularjs.org/api/ng/input/input%5Bemail%5D.  Have 
you looked at this?  You can overcome 'yelling' at the user if you make a 
minor change.  Instead of blank space converting to error text (and the 
inadvertent scrolling), perhaps consider a hint (add email) above your 
input (and maybe forego the input placeholder).  This way, you don't have 
to worry about jumping fields.  This seem to be the easiest & appropriate 
solution.  Is there a reason you can't use a hint text that converts to 
GOOD!  instead of blank area that converts to BAD! and jumps...? Just 
looking at this conversely.

Mo
On Thursday, July 16, 2015 at 12:32:36 PM UTC-4, Kevin W wrote:
>
> Mo -
>
> We considered that but the user experience using that model is horrible 
> for fields that aren't simple required/not required.  For example, an email 
> field will show an error as soon as you type your first character (before 
> the user has even finished).  It's not good to "yell" at the user before 
> they're done.  That's why we moved to the onblur.
>
> Thanks,
> Kevin
>
>
>
> On Thursday, July 16, 2015 at 8:28:19 AM UTC-6, Mo Moadeli (CREDACIOUS) 
> wrote:
>
>> Kevin, you may want consider exchanging handling the blur (handled via 
>> $touched I assume) and perhaps explore showing errors 'as you type' via 
>> ng-change for example that get triggered on every keypress (as opposed to 
>> ket release) and then incorporate it into your form validation (eg:
>> https://docs.angularjs.org/api/ng/input/input%5Btext%5D). Usually, there 
>> are better ways than incorporating synthetic delays for these situations.
>>
>> Mo
>>
>> On Wednesday, July 15, 2015 at 6:48:43 PM UTC-4, Kevin W wrote:
>>>
>>> We are using the AngularJS validation framework for client side 
>>> validation.
>>>
>>> The layout of our page causes the errors to appear and disappear when 
>>> fields lose focus.
>>>
>>> The problem we are having is if you have an error being displayed, and 
>>> you correct the field but do not leave the field, then scroll down to the 
>>> submit button, when you click the submit button the angular validation 
>>> fires and removes the error which causes the contents of the page to 
>>> "shift" up just enough that the button click doesn't occur.
>>>
>>> Is there a way to tell Angular to delay the hiding of the validation 
>>> errors so that (A) the form would still be considered valid and (B) the 
>>> button click event could occur as expected.
>>>
>>> Thanks,
>>> Kevin
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

Reply via email to